Linux-libre is a modified version of the Linux kernel that contains no binary blobs, obfuscated code, or code released under proprietary licenses.[8] In the Linux kernel, they are mostly used for proprietary firmware images. While generally redistributable, binary blobs do not give the user the freedom to audit, modify, or, consequently, redistribute their modified versions. The GNU Project keeps Linux-libre in synchronization with the mainline Linux kernel.[9]Linux-libre 是 Linux 内核的修改版本，不包含二进制 blob、混淆代码或在专有许可下发布的代码。 [8]在 Linux 内核中，它们主要用于专有固件映像。虽然通常可重新分发，但二进制 blob 不赋予用户审计、修改或因此重新分发其修改后版本的自由。 GNU 项目使 Linux-libre 与主线 Linux 内核保持同步。 [9]
The Linux kernel started to include binary blobs in 1996.[10] The work to clear out the binary blobs began in 2006 with gNewSense's find-firmware and gen-kernel. This work was taken further by the BLAG Linux distribution in 2007 when deblob and Linux-libre was born.[11][12]Linux 内核于 1996 年开始包含二进制 blob。 [10]清除二进制 blob 的工作始于 2006 年 gNewSense 的 find-firmware 和 gen-kernel。 2007 年，当 deblob 和 Linux-libre 诞生时，BLAG Linux 发行版进一步推进了这项工作。 [11][12]
Linux-libre was first released by the Free Software Foundation Latin America (FSFLA), then endorsed by the Free Software Foundation (FSF)[13] as a valuable component for the totally free Linux distributions. It became a GNU package in March 2012.[14]Alexandre Oliva is the project maintainer.
Linux-libre 最初由拉丁美洲自由软件基金会 (FSFLA) 发布，然后由自由软件基金会 (FSF)[13] 认可为完全免费的 Linux 发行版的重要组成部分。它于 2012 年 3 月成为 GNU 软件包。 [14] Alexandre Oliva 是项目维护者。
The removal process is achieved by using a script called deblob-main.[15] This script is inspired by the one used for gNewSense. Jeff Moe made subsequent modifications to meet certain requirements for its use with the BLAG Linux and GNU distribution. There is another script called deblob-check,[16] which is used to check if a kernel source file, a patch or a compressed sources file still contains software which is suspected of being proprietary.
删除过程是通过使用名为 deblob-main 的脚本来实现的。 [15]该脚本的灵感来自于用于 gNewSense 的脚本。 Jeff Moe 进行了后续修改以满足其与 BLAG Linux 和 GNU 发行版一起使用的某些要求。还有另一个脚本称为 deblob-check，[16] 用于检查内核源文件、补丁或压缩源文件是否仍然包含被怀疑是专有的软件。
Aside from the primary intended effect of running a system with only free software, the practical consequences of removing device firmware that a user is not allowed to study or modify has both positive and negative effects.
除了仅使用免费软件运行系统的主要预期效果外，删除不允许用户研究或修改的设备固件的实际后果既有积极的影响，也有消极的影响。
Removal of device firmware can be considered an advantage for security and stability, when the firmware cannot be audited for bugs, for security problems, and for malicious operations such as backdoors, or when the firmware cannot be fixed by the Linux kernel maintainers themselves, even if they know of problems. It is possible for the entire system to be compromised by a malicious firmware, and without the ability to perform a security audit on manufacturer-provided firmware, even an innocent bug could undermine the safety of the running system.[17]删除设备固件可以被认为是安全和稳定的优势，当固件无法审计错误、安全问题和恶意操作（如后门）时，或者当固件不能由 Linux 内核维护者自己修复时，甚至如果他们知道有问题。整个系统有可能被恶意固件破坏，如果无法对制造商提供的固件执行安全审计，即使是无辜的错误也可能破坏运行系统的安全性。 [17]
Removing proprietary firmware from the kernel will cause loss of functionality of certain hardware that does not have a free software replacement available.[9] This affects certain sound, video, TV tuner, and network cards, especially in the case of recent Intel Wi-Fi cards and recent nVidia graphics cards, as well as some other devices. When possible, free software replacement firmware is provided as a substitute,[9][18] such as the openfwwf[19] for b43, carl9170[20] and ath9k_htc[21]wireless card drivers. Reviewer Ramces Red summarized the issue with Linux-Libre, writing, "it does not always have the best hardware support."[9]从内核中删除专有固件将导致某些没有免费软件替代的硬件失去功能。 [9]这会影响某些声音、视频、电视调谐器和网卡，尤其是最近的 Intel Wi-Fi 卡和最近的 nVidia 显卡，以及一些其他设备。如果可能，提供免费软件替换固件作为替代，[9][18] 例如用于 b43 的 openfwwf[19]、carl9170[20] 和 ath9k_htc[21] 无线网卡驱动程序。评论员 Ramces Red 总结了 Linux-Libre 的问题，写道：“它并不总是拥有最好的硬件支持。”[9]
Linux-libre does not suggest the user install CPU microcode update bundles, since the code is proprietary.[22] Microcode update bundles have been used in the Linux kernel version, among other things, to mitigate hardware vulnerabilities.[23]Linux-libre 不建议用户安装 CPU 微代码更新包，因为该代码是专有的。 [22]微码更新包已在 Linux 内核版本中使用，除其他外，以减轻硬件漏洞。 [23]
The source code and precompiled packages of the deblobbed Linux kernel are available directly from the distributions which use the Linux-libre scripts. Freed-ora is a subproject which prepares and maintains RPM packages based on Fedora.[24] There are also precompiled packages for Debian[25] and derived distributions such as Ubuntu.[26]去斑点 Linux 内核的源代码和预编译包可以直接从使用 Linux-libre 脚本的发行版中获得。 Freed-ora 是一个基于 Fedora 准备和维护 RPM 包的子项目。 [24]还有用于 Debian[25] 和派生发行版（如 Ubuntu）的预编译包。[26]
Distributions that compile a free Linux kernel[edit]编译免费 Linux 内核的发行版[编辑]
These distros do not use the packaged Linux-libre but instead completely remove binary blobs from the mainline Linux kernel. The source is then compiled and the resulting free Linux kernel is used by default in these systems:
这些发行版不使用打包的 Linux-libre，而是从主线 Linux 内核中完全删除二进制 blob。然后编译源代码，并在这些系统中默认使用生成的免费 Linux 内核：
gNewSense[34] (It was based on Debian.)gNewSense[34]（它基于 Debian。）
Canaima[35] (It was based on Debian.)Canaima[35]（它基于 Debian。）
Linux-libre as an alternative kernel[edit]Linux-libre 作为替代内核[编辑]
Distributions in which Linux is the default kernel used and which propose Linux-libre as an alternative kernel:
以 Linux 为默认内核并建议使用 Linux-libre 作为替代内核的发行版：
^ Jump up to: abcdRed, Ramces (March 22, 2022). "5 Best Linux-Libre Distributions for Better Security". Make Tech Easier. Archived from the original on April 30, 2022. Retrieved April 30, 2022.^
跳转至：
a b c d Red，Ramces（2022 年 3 月 22 日）。 “提高安全性的 5 个最佳 Linux-Libre 发行版”。让技术更容易。原始存档于 2022 年 4 月 30 日。2022 年 4 月 30 日检索。
^Free Software Foundation. "Linux (BLOB free version)". Free Software Directory. Retrieved December 6, 2011. [...] in the interest of freedom, we are providing a link to a version of the kernel in which this proprietary code has been removed so that it is entirely free software^ 自由软件基金会。 “Linux（BLOB 免费版）”。自由软件目录。 2011 年 12 月 6 日检索。[...] 为了自由，我们提供了一个内核版本的链接，该内核版本已删除此专有代码，因此它是完全免费的软件
^Free Software Foundation Latin America. "How it is done". Linux-libre, Free as in Freedo. Retrieved December 6, 2011.^ 拉丁美洲自由软件基金会。 “它是如何完成的”。 Linux-libre，像 Freedo 一样免费。 2011 年 12 月 6 日检索。
^Free Software Foundation Latin America. "Linux-libre's Freed-ora project". Retrieved December 6, 2011. Freed-ora is a sub-project that prepares and maintains 100% Free RPMs that track Fedora's non-Free kernels^ 拉丁美洲自由软件基金会。 “Linux-libre 的 Freed-ora 项目”。 2011 年 12 月 6 日检索。Freed-ora 是一个子项目，它准备和维护跟踪 Fedora 非自由内核的 100% 自由 RPM
^Millan, Robert (April 23, 2009). "Linux-libre for Debian Lenny". [Debian Mailing Lists] Announcements for developers (Mailing list). Retrieved May 12, 2009. This is to announce that Debian packages of Linux-libre [...] are now available for Lenny users who want to use them [...]^ Millan, Robert（2009 年 4 月 23 日）。 “用于 Debian Lenny 的 Linux-libre”。 [Debian 邮件列表] 开发者公告（邮件列表）。 2009 年 5 月 12 日检索。这是为了宣布 Debian 软件包的 Linux-libre [...] 现在可供想要使用它们的 Lenny 用户使用 [...]
GNU Hurd is a collection of microkernel servers written as part of GNU, for the GNU Mach microkernel. It has been under development since 1990 by the GNU Project of the Free Software Foundation, designed as a replacement for the Unix kernel,[3] and released as free software under the GNU General Public License. When the Linux kernel proved to be a viable solution, development of GNU Hurd slowed, at times alternating between stasis and renewed activity and interest.[4]GNU Hurd 是作为 GNU 的一部分编写的微内核服务器的集合，用于 GNU Mach 微内核。它自 1990 年以来一直由自由软件基金会的 GNU 项目开发，旨在替代 Unix 内核，[3] 并根据 GNU 通用公共许可证作为免费软件发布。当 Linux 内核被证明是一个可行的解决方案时，GNU Hurd 的开发速度放慢了，有时在停滞和新的活动和兴趣之间交替。 [4]
The Hurd's design consists of a set of protocols and server processes (or daemons, in Unix terminology) that run on the GNU Mach microkernel.[3] The Hurd aims to surpass the Unix kernel in functionality, security, and stability, while remaining largely compatible with it. The GNU Project chose the multiserver microkernel[5] for the operating system, due to perceived advantages over the traditional Unix monolithic kernel architecture,[6] a view that had been advocated by some developers in the 1980s.[4]Hurd 的设计包括一组在 GNU Mach 微内核上运行的协议和服务器进程（或 Unix 术语中的守护进程）。 [3] Hurd 的目标是在功能、安全性和稳定性方面超越 Unix 内核，同时保持与其基本兼容。 GNU 项目为操作系统选择了多服务器微内核[5]，因为它比传统的 Unix 单片内核架构具有明显的优势，[6] 这种观点在 1980 年代被一些开发人员所提倡。 [4]
In December 1991 the primary architect of the Hurd described the name as a mutuallyrecursive acronym:[7]1991 年 12 月，赫德的主要架构师将该名称描述为相互递归的首字母缩略词：[7]
It's time [to] explain the meaning of "Hurd". "Hurd" stands for "Hird of Unix-Replacing Daemons". And, then, "Hird" stands for "Hurd of Interfaces Representing Depth". We have here, to my knowledge, the first software to be named by a pair of mutually recursive acronyms.是时候[解释]“Hurd”的含义了。 “Hurd”代表“Hird of Unix-Replacing Daemons”。然后，“Hird”代表“Hurd of Interfaces Representing Depth”。据我所知，我们这里有第一个由一对相互递归的首字母缩略词命名的软件。
As both hurd and hird are homophones of the English word herd, the full name GNU Hurd is also a play on the words herd of gnus, reflecting how the kernel works.[8]由于 hurd 和 hird 都是英文单词 herd 的同音词，因此全名 GNU Hurd 也是 gnus 的 herd 一词的变体，反映了内核的工作原理。 [8]
The logo is called the Hurd boxes and it also reflects on architecture. The logo is a graph where nodes represent the Hurd kernel's servers and directed edges are IPC messages.[7]这个标志被称为赫德盒子，它也反映在建筑上。徽标是一个图形，其中节点代表 Hurd 内核的服务器，有向边是 IPC 消息。 [7]
Richard Stallman founded the GNU Project in September 1983 with an aim to create a freeGNU operating system. Initially the components required for kernel development were written: editors, shell, compiler, debugger etc. By 1989, the GNU GPL came into being and the only major component missing was the kernel.[9][10]Richard Stallman 于 1983 年 9 月创立了 GNU 项目，旨在创建一个免费的 GNU 操作系统。最初编写内核开发所需的组件：编辑器、shell、编译器、调试器等。到 1989 年，GNU GPL 应运而生，唯一缺少的主要组件是内核。[9][10]
Development on the Hurd began in 1990 after an abandoned kernel attempt in 1986, based on the research TRIX operating system developed by Professor Steve Ward and his group at MIT'sLaboratory for Computer Science (LCS).[11] According to Thomas Bushnell, the initial Hurd architect, their early plan was to adapt the 4.4BSD-Lite kernel and, in hindsight, "It is now perfectly obvious to me that this would have succeeded splendidly and the world would be a very different place today."[12] In 1987 Richard Stallman proposed using the Mach microkernel developed by Richard Rashid at Carnegie Mellon University. Work on this was delayed for three years due to uncertainty over whether CMU would release the Mach code under a suitable license.[11]在 1986 年放弃内核尝试之后，Hurd 的开发始于 1990 年，基于 Steve Ward 教授和他在麻省理工学院计算机科学实验室 (LCS) 的研究小组开发的 TRIX 操作系统。 [11]根据 Hurd 最初的架构师 Thomas Bushnell 的说法，他们的早期计划是采用 4.4BSD-Lite 内核，事后看来，“现在对我来说非常明显，这会取得巨大的成功，世界将会变得非常不同[12] 1987 年，Richard Stallman 提议使用卡内基梅隆大学的 Richard Rashid 开发的 Mach 微内核。由于不确定 CMU 是否会在适当的许可下发布 Mach 代码，这方面的工作被推迟了三年。 [11]
With the release of the Linux kernel in 1991, the primary user of GNU's userland components soon became operating systems based on the Linux kernel (Linux distributions), prompting the coining of the term GNU/Linux.
随着 1991 年 Linux 内核的发布，GNU 用户空间组件的主要用户很快变成了基于 Linux 内核的操作系统（Linux 发行版），这促使了 GNU/Linux 一词的诞生。
Development of the Hurd has proceeded slowly. Despite an optimistic announcement by Stallman in 2002 predicting a release of GNU/Hurd later that year,[13] the Hurd is still not considered suitable for production environments. Development in general has not met expectations, and there are still a significant number of bugs and missing features.[14] This has resulted in a poorer product than many, including Stallman, had expected.[15] In 2010, after twenty years under development, Stallman said that he was "not very optimistic about the GNU Hurd. It makes some progress, but to be really superior it would require solving a lot of deep problems", but added that "finishing it is not crucial" for the GNU system because a free kernel already existed (Linux), and completing Hurd would not address the main remaining problem for a free operating system: device support.[16]赫德的发展进展缓慢。尽管 Stallman 在 2002 年发表了乐观的声明，预测该年晚些时候将发布 GNU/Hurd，[13] Hurd 仍然被认为不适合生产环境。总体发展没有达到预期，仍然存在大量错误和缺失的功能。 [14]这导致产品比许多人（包括斯托曼）预期的要差。 [15] 2010 年，经过 20 年的发展，Stallman 说他“对 GNU Hurd 不是很看好。它取得了一些进步，但要真正优秀它需要解决很多深层次的问题”，但补充说“完成它对 GNU 系统来说并不重要”，因为自由内核已经存在 (Linux)，完成 Hurd 不会解决自由操作系统的主要遗留问题：设备支持。 [16]
The Debian project, among others, have worked on the Hurd project to produce binary distributions of Hurd-based GNU operating systems for IBM PC compatible systems.
Debian 项目和其他项目一起致力于 Hurd 项目，为 IBM PC 兼容系统生产基于 Hurd 的 GNU 操作系统的二进制发行版。
After years of stagnation, development picked up again in 2015 and 2016, with four releases during these two years.[17]经过多年的停滞，开发在 2015 年和 2016 年再次回升，在这两年中发布了四个版本。 [17]
On August 20, 2015, amid the Google Summer of Code, it was announced that GNU Guix had been ported to GNU Hurd.[18]2015 年 8 月 20 日，在 Google 代码之夏期间，宣布 GNU Guix 已移植到 GNU Hurd。 [18]
General structure of monolithic, microkernel and hybrid kernel-based operating systems, respectively.分别是基于单片、微内核和混合内核的操作系统的一般结构。
Unlike most Unix-like kernels, the Hurd uses a server–client architecture, built on a microkernel that is responsible for providing the most basic kernel services – coordinating access to the hardware: the CPU (through process management and scheduling), RAM (via memory management), and other various input/output devices (via I/O scheduling) for sound, graphics, mass storage, etc. In theory, the microkernel design would allow for all device drivers to be built as servers working in user space, but today most drivers of this kind are still contained in the GNU Machkernel space.[19]与大多数类 Unix 内核不同，Hurd 使用服务器-客户端架构，建立在微内核之上，微内核负责提供最基本的内核服务——协调对硬件的访问：CPU（通过进程管理和调度）、RAM（通过内存管理）和其他各种输入/输出设备（通过 I/O 调度），用于声音、图形、大容量存储等。理论上，微内核设计将允许所有设备驱动程序构建为在用户空间中工作的服务器，但今天大多数此类驱动程序仍包含在 GNU Mach 内核空间中。 [19]
According to Hurd developers, the main advantage of microkernel-based design is the ability to extend the system: developing a new module would not require in depth knowledge of the rest of the kernel, and a bug in one module would not crash the entire system. Hurd provides a concept of translators, a framework of modules used to extend a file system functionality.[20]根据 Hurd 开发人员的说法，基于微内核的设计的主要优点是能够扩展系统：开发新模块不需要深入了解内核的其余部分，并且一个模块中的错误不会导致整个系统崩溃.赫德提供了翻译器的概念，即用于扩展文件系统功能的模块框架。 [20]
From early on, the Hurd was developed to use GNU Mach as the microkernel. This was a technical decision made by Richard Stallman, who thought it would speed up the work by saving a large part of it. He has admitted that he was wrong about that.[21] Other Unix-like systems working on the Mach microkernel include OSF/1, Lites, and MkLinux. macOS and NeXTSTEP use hybrid kernels based on Mach.
从早期开始，Hurd 就被开发为使用 GNU Mach 作为微内核。这是 Richard Stallman 做出的一项技术决定，他认为这样可以通过节省大部分工作来加快工作速度。他承认自己错了。 [21]其他在 Mach 微内核上运行的类 Unix 系统包括 OSF/1、Lites 和 MkLinux。 macOS 和 NeXTSTEP 使用基于 Mach 的混合内核。
From 2004 onward, various efforts were launched to port the Hurd to more modern microkernels. The L4 microkernel was the original choice in 2004, but progress slowed to a halt. Nevertheless, during 2005, Hurd developer Neal Walfield finished the initial memory management framework for the L4/Hurd port, and Marcus Brinkmann ported essential parts of glibc; namely, getting the process startup code working, allowing programs to run, thus allowing the first user programs (trivial ones such as the hello world program) in C to run.
从 2004 年开始，各种努力将 Hurd 移植到更现代的微内核。 L4 微内核是 2004 年的最初选择，但进展放缓直至停滞。尽管如此，在 2005 年期间，Hurd 开发人员 Neal Walfield 完成了 L4/Hurd 端口的初始内存管理框架，而 Marcus Brinkmann 移植了 glibc 的重要部分；即，让进程启动代码工作，允许程序运行，从而允许 C 中的第一个用户程序（如 hello world 程序这样的普通程序）运行。
Since 2005, Brinkmann and Walfield started researching Coyotos as a new kernel for HURD.[22][23] In 2006, Brinkmann met with Jonathan Shapiro (a primary architect of the Coyotos Operating System) to aid in and discuss the use of the Coyotos kernel for GNU/Hurd. In further discussion HURD developers realised that Coyotos (as well as other similar kernels) are not suitable for HURD.[24]自 2005 年以来，Brinkmann 和 Walfield 开始研究 Coyotos 作为 HURD 的新内核。 [22][23] 2006 年，Brinkmann 会见了 Jonathan Shapiro（Coyotos 操作系统的主要架构师），以帮助讨论 Coyotos 内核在 GNU/Hurd 中的使用。在进一步讨论中，HURD 开发人员意识到 Coyotos（以及其他类似内核）不适合 HURD。 [24]
In 2007, Hurd developers Neal Walfield and Marcus Brinkmann gave a critique of the Hurd architecture, known as "the critique",[25] and a proposal for how a future system may be designed, known as "the position paper".[26] In 2008, Neal Walfield began working on the Viengoos microkernel as a modern native kernel for HURD. As of 2009, development on Viengoos is paused due to Walfield lacking time to work on it.[27]2007 年，Hurd 开发人员 Neal Walfield 和 Marcus Brinkmann 对 Hurd 架构提出了批评，称为“批评”，[25] 以及关于如何设计未来系统的建议，称为“立场文件”[26]。 ] 2008 年，Neal Walfield 开始研究 Viengoos 微内核，作为 HURD 的现代原生内核。截至 2009 年，由于 Walfield 没有时间进行开发，Viengoos 的开发暂停了。 [27]
In the meantime, others have continued working on the Mach variant of Hurd.[28]与此同时，其他人继续研究赫德的 Mach 变体。 [28]
A number of traditional Unix concepts are replaced or extended in the Hurd.
许多传统的 Unix 概念在 Hurd 中被替换或扩展。
Under Unix, every running program has an associated user id, which normally corresponds to the user that started the process. This id largely dictates the actions permitted to the program. No outside process can change the user id of a running program. A Hurd process, on the other hand, runs under a set of user ids, which can contain multiple ids, one, or none. A sufficiently privileged process can add and remove ids to another process. For example, there is a password server that will hand out ids in return for a correct login password.
在 Unix 下，每个正在运行的程序都有一个关联的用户 ID，通常对应于启动该进程的用户。这个 id 在很大程度上决定了程序允许的操作。没有外部进程可以更改正在运行的程序的用户标识。另一方面，Hurd 进程在一组用户 ID 下运行，这些用户 ID 可以包含多个 ID，一个或一个都没有。足够特权的进程可以向另一个进程添加和删除 ID。例如，有一个密码服务器会分发 id 以换取正确的登录密码。
Regarding the file system, a suitable program can be designated as a translator for a single file or a whole directory hierarchy. Every access to the translated file, or files below a hierarchy in the second case, is in fact handled by the program. For example, a file translator may simply redirect read and write operations to another file, like a Unix symbolic link. The effect of Unix mounting is achieved by setting up a filesystem translator (using the "settrans" command). Translators can also be used to provide services to the user. For example, the ftpfs translator allows a user to encapsulate remote FTP sites within a directory. Then, standard tools such as ls, cp, and rm can be used to manipulate files on the remote system. Even more powerful translators are ones such as UnionFS, which allows a user to unify multiple directories into one; thus listing the unified directory reveals the contents of all the directories.
关于文件系统，可以指定合适的程序作为单个文件或整个目录层次结构的翻译器。在第二种情况下，对已翻译文件或层次结构下的文件的每次访问实际上都由程序处理。例如，文件翻译器可能只是将读写操作重定向到另一个文件，如 Unix 符号链接。 Unix 挂载的效果是通过设置文件系统翻译器（使用“settrans”命令）来实现的。翻译器也可以用来为用户提供服务。例如，ftpfs 转换器允许用户将远程 FTP 站点封装在一个目录中。然后，可以使用 ls、cp 和 rm 等标准工具来操作远程系统上的文件。更强大的翻译器是 UnionFS，它允许用户将多个目录统一为一个；因此列出统一目录会显示所有目录的内容。
The Hurd requires a multiboot-compliant boot loader, such as GRUB.
Hurd 需要兼容多重引导的引导加载程序，例如 GRUB。
According to the Debian documentation, there are 24 servers (18 core servers and 6 file system servers) named as follows:[29]根据 Debian 文档，有 24 个服务器（18 个核心服务器和 6 个文件系统服务器）命名如下：[29]
auth (authentication server): Receives requests and passwords from programs and gives them an ID, which changes the privileges of the program.auth（认证服务器）：接收来自程序的请求和密码，并给他们一个ID，这改变了程序的权限。
crash (crash server): Handles all fatal errors.crash（崩溃服务器）：处理所有致命错误。
exec (execution server): Translates an executable image (currently ELF and a.out are supported) to a runnable image in memory.exec（执行服务器）：将可执行映像（目前支持 ELF 和 a.out）转换为内存中的可运行映像。
fifo (FIFO translator): Implements named pipes.fifo（FIFO 翻译器）：实现命名管道。
new-fifo (new FIFO server): An alternate server for named pipes.new-fifo（新 FIFO 服务器）：命名管道的备用服务器。
firmlink (the firmlink translator): Implements firmlinks ‒ "half-way between a symbolic link and a hard link".[30]firmlink（firmlink 翻译器）：实现 firmlinks——“符号链接和硬链接之间的中间路径”。[30]
fwd (forward server): Forwards requests to other servers, used by fifo and symlink servers.fwd（转发服务器）：将请求转发到其他服务器，供fifo和symlink服务器使用。
ifsock (server for sockets interface): Helps with UNIX domain socket addresses.ifsock（套接字接口服务器）：帮助处理 UNIX 域套接字地址。
init (init server): Basic system booting and configuration.init (init server)：基本的系统引导和配置。
magic (magic server): Signals that a name lookup must be resolved internally by a process when the result involves the process's state.magic（魔法服务器）：当结果涉及进程的状态时，表明名称查找必须由进程在内部解析。
null (null server): Implements /dev/null and /dev/zero.null（空服务器）：实现/dev/null 和/dev/zero。
The ext2 filesystem translator. It receives disk blocks from the microkernel and gives files and directories to the applications.ext2 文件系统转换器。它从微内核接收磁盘块并将文件和目录提供给应用程序。
isofsISOFS
The translator for the ISO 9660 filesystem. Translates blocks of a CD or DVD to files and directories for the applications.ISO 9660 文件系统的转换器。将 CD 或 DVD 的块转换为应用程序的文件和目录。
The servers collectively implement the POSIXAPI, with each server implementing a part of the interface. For instance, the various filesystem servers each implement the filesystem calls. The storage server will work as a wrapping layer, similar to the block layer of Linux. The equivalent of VFS of Linux is achieved by libdiskfs and libpager libraries.
服务器共同实现 POSIX API，每个服务器实现接口的一部分。例如，各种文件系统服务器各自实现文件系统调用。存储服务器将作为一个包装层，类似于 Linux 的块层。相当于 Linux 的 VFS 是通过 libdiskfs 和 libpager 库实现的。
GNU distributions running Hurd[edit]运行 Hurd 的 GNU 发行版[编辑]
^Stallman, Richard (2006-03-09). "The Free Software Movement and the Future of Freedom"(ogg). Free Software Foundation. Zagreb. This is the way, also, that people thought was the cleanest possible way to design kernels back in 1990. Well, it took many many many years to get this kernel to run at all, and it still doesn't run well, and it looks like there may be fundamental problems with this design, which nobody knew about back in 1990.
^Stallman, Richard (2000-10-12). "In Defense of Red Hat". Linux Today. Retrieved 2011-12-07. I take full responsibility for the technical decision to develop the GNU kernel based on Mach, a decision which seems to have been responsible for the slowness of the development. I thought using Mach would speed the work by saving us a large part of the job, but I was wrong.^ 斯托曼，理查德 (2000-10-12)。 “为红帽辩护”。今天的Linux。检索于 2011-12-07。我对基于 Mach 开发 GNU 内核的技术决定负全部责任，这个决定似乎是导致开发缓慢的原因。我认为使用 Mach 可以节省我们的大部分工作，从而加快工作速度，但我错了。
^Shapiro, Jonathan S. (2005-10-27). "Re: A comment about changing kernels". l4-hurd (Mailing list).^ 夏皮罗，乔纳森 S. (2005-10-27)。 “回复：关于更改内核的评论”。 l4-hurd（邮件列表）。
^Bachmann, Tom (2006-07-07). "Re: seL4, L4.sec and coyotos mess". l4-hurd (Mailing list).^ 汤姆·巴赫曼 (2006-07-07)。 “回复：seL4、L4.sec 和郊狼一团糟”。 l4-hurd（邮件列表）。
GNU variants (also called GNU distributions or distros for short) are operating systems based upon the GNU operating system[1][2][3][4][5] (the Hurd kernel, the GNU C library, system libraries and application software like GNU coreutils, bash, GNOME, the Guix package manager, etc). According to the GNU project and others, these also include most operating systems using the Linux kernel and a few others using BSD-based kernels.[6][7][2]GNU 变体（也称为 GNU 发行版或简称发行版）是基于 GNU 操作系统[1][2][3][4][5]（Hurd 内核、GNU C 库、系统库和应用程序）的操作系统GNU coreutils、bash、GNOME、Guix 包管理器等软件）。根据 GNU 项目和其他人的说法，这些还包括大多数使用 Linux 内核的操作系统和一些其他使用基于 BSD 内核的操作系统。 [6][7][2]
GNU users usually obtain their operating system by downloading GNU distributions, which are available for a wide variety of systems ranging from embedded devices (for example, LibreCMC) and personal computers (for example, Debian GNU/Hurd) to powerful supercomputers (for example, Rocks Cluster Distribution).
GNU 用户通常通过下载 GNU 发行版来获得他们的操作系统，这些发行版可用于从嵌入式设备（例如，LibreCMC）和个人计算机（例如，Debian GNU/Hurd）到强大的超级计算机（例如，岩石群分布）。
Hurd is the official kernel developed for the GNU system (before Linux-libre also became an official GNU package). Debian GNU/Hurd was discussed for a release as technology preview with Debian 7.0 Wheezy, however these plans were discarded due to the immature state of the system.[8] However the maintainers of Debian GNU/Hurd decided to publish an unofficial release on the release date of Debian 7.0. Debian GNU/Hurd is not considered yet to provide the performance and stability expected from a production system. Among the open issues are incomplete implementation of Java and X.org graphical user interfaces and limited hardware driver support.[9] About two thirds of the Debian packages have been ported to Hurd.[10]Hurd 是为 GNU 系统开发的官方内核（在 Linux-libre 也成为官方 GNU 包之前）。 Debian GNU/Hurd 被讨论作为 Debian 7.0 Wheezy 的技术预览发布，但是由于系统的不成熟状态，这些计划被放弃了。 [8]然而，Debian GNU/Hurd 的维护者决定在 Debian 7.0 发布日期发布一个非官方版本。 Debian GNU/Hurd 尚未被认为能够提供生产系统所期望的性能和稳定性。未解决的问题包括 Java 和 X.org 图形用户界面的不完整实现以及有限的硬件驱动程序支持。 [9]大约三分之二的 Debian 软件包已经移植到 Hurd。 [10]
Arch Hurd is a derivative work of Arch Linux, porting it to the GNU Hurd system with packages optimised for the Intel P6 architecture. Their goal is to provide an Arch-like user environment (BSD-style init scripts, pacman package manager, rolling releases, and a simple set up) on the GNU Hurd, which is stable enough for at least occasional use. Currently it provides a LiveCD for evaluation purposes and installation guides for LiveCD and conventional installation.[11][12][13]Arch Hurd 是 Arch Linux 的衍生作品，将其移植到 GNU Hurd 系统，并带有针对 Intel P6 架构优化的软件包。他们的目标是在 GNU Hurd 上提供一个类似 Arch 的用户环境（BSD 风格的初始化脚本、pacman 包管理器、滚动发布和简单的设置），它足够稳定，至少可以偶尔使用。目前，它提供了用于评估目的的 LiveCD 以及 LiveCD 和常规安装的安装指南。[11][12][13]
The term GNU/Linux or GNU+Linux is used by the FSF and its supporters to refer to an operating system where the Linux kernel is distributed with a GNU system software. Such distributions are the primary installed base of GNU packages and programs and also of Linux. The most notable official use of this term for a distribution is Debian GNU/Linux.
FSF 及其支持者使用术语 GNU/Linux 或 GNU+Linux 来指代 Linux 内核与 GNU 系统软件一起分发的操作系统。这些发行版是 GNU 软件包和程序以及 Linux 的主要安装基础。 Debian GNU/Linux 中最著名的正式使用此术语的发行版。
As of 2018, the only GNU variants recommended by the GNU Project for regular use are Linux distributions committed to the Free System Distribution Guidelines; most of which refer to themselves as "GNU/Linux" (like Debian), and actually use a deblobbed version of the Linux kernel (like the Linux-libre kernel) and not the mainline Linux kernel.[14]截至 2018 年，GNU 项目推荐用于常规使用的唯一 GNU 变体是遵守自由系统分发指南的 Linux 发行版；其中大部分自称为“GNU/Linux”（如 Debian），实际上使用的是去斑点版本的 Linux 内核（如 Linux-libre 内核），而不是主线 Linux 内核。 [14]
Debian GNU/kFreeBSD is an operating system for IA-32 and x86-64 computer architectures. It is a distribution of GNU with Debian package management and the kernel of FreeBSD. The k in kFreeBSD is an abbreviation for kernel of,[15] and reflects the fact that only the kernel of the complete FreeBSD operating system is used. The operating system was officially released with Debian Squeeze (6.0) on February 6, 2011.[16] One Debian GNU/kFreeBSD live CD is Ging, which is no longer maintained.[17]Debian GNU/kFreeBSD 是一个用于 IA-32 和 x86-64 计算机架构的操作系统。它是带有 Debian 包管理和 FreeBSD 内核的 GNU 发行版。 kFreeBSD 中的 k 是 kernel of,[15] 的缩写，反映了仅使用完整 FreeBSD 操作系统的内核这一事实。该操作系统于 2011 年 2 月 6 日随 Debian Squeeze (6.0) 一起正式发布。 [16]一张 Debian GNU/kFreeBSD live CD 是 Ging，不再维护。 [17]
Debian GNU/NetBSDDebian GNU/NetBSD was an experimental port of GNU user-land applications to NetBSD kernel. No official release of this operating system was made; although work was conducted on ports for the IA-32[18] and DEC Alpha[19] architectures, it has not seen active maintenance since 2002 and is no longer available for download.[20]是 GNU 用户态应用程序到 NetBSD 内核的实验性端口。该操作系统没有正式发布；尽管在 IA-32[18] 和 DEC Alpha[19] 架构的端口上进行了工作，但自 2002 年以来就没有进行过主动维护，并且不再可供下载。 [20]
As of September 2020, the GNU Project does not recommend or endorse any BSD operating systems.[21]截至 2020 年 9 月，GNU 项目不推荐或认可任何 BSD 操作系统。 [21]
Nexenta OS is the first distribution that combines the GNU userland (with the exception of libc; OpenSolaris' libc is used) and Debian's packaging and organisation with the OpenSolaris kernel. Nexenta OS is available for IA-32 and x86-64 based systems. Nexenta Systems, Inc initiated the project and sponsors its continued development.[22]
Nexenta OS is not considered a GNU variant, due to the use of OpenSolaris libc. Multiple Illumos distributions use GNU userland by default.[23]Nexenta OS 是第一个将 GNU 用户区（libc 除外；使用 OpenSolaris 的 libc）和 Debian 的打包和组织与 OpenSolaris 内核相结合的发行版。 Nexenta OS 可用于基于 IA-32 和 x86-64 的系统。 Nexenta Systems, Inc 发起了该项目并资助其持续发展。 [22]由于使用了 OpenSolaris libc，Nexenta OS 不被视为 GNU 变体。多个 Illumos 发行版默认使用 GNU userland。 [23]
The Cygwin project is an actively-developed compatibility layer in the form of a C library providing a substantial part of the POSIXAPI functionality for Windows, as well as a distribution of GNU and other Unix-like programs for such an ecosystem. It was first released in 1995 by Cygnus Solutions (now Red Hat).
Cygwin 项目是一个以 C 库形式积极开发的兼容层，为 Windows 提供大部分 POSIX API 功能，并为此类生态系统分发 GNU 和其他类 Unix 程序。它于 1995 年由 Cygnus Solutions（现为 Red Hat）首次发布。
In 2016 Microsoft and Canonical added an official compatibility layer to Windows 10 that translates Linux kernel calls into Windows NT ones, the reverse of what Wine does. This allows ELF executables to run unmodified on Windows, and is intended to provide web developers with the more familiar GNU userland on top of the Windows kernel.[24][25][26] The combination has been dubbed "Linux for Windows", even though Linux (i.e. the operating system family defined by its common use of the Linux kernel) is absent.
2016 年，Microsoft 和 Canonical 向 Windows 10 添加了一个官方兼容层，将 Linux 内核调用转换为 Windows NT 调用，这与 Wine 所做的相反。这允许 ELF 可执行文件在 Windows 上运行而无需修改，旨在为 Web 开发人员提供更熟悉的 Windows 内核之上的 GNU 用户空间。[24][25][26]该组合被称为“Windows 版 Linux”，尽管 Linux（即由其通常使用 Linux 内核定义的操作系统系列）并不存在。
^ Jump up to: abUG, Awesome Developers. "Source Code & GPL Open Source". www.snom.com. Retrieved 2018-04-08. Variants of the GNU operating system, which use the kernel Linux, are now widely used; though these systems are often referred to as "Linux", they are more accurately called "GNU/Linux systems".^ 跳转至： a b UG, Awesome Developers。 “源代码和 GPL 开源”。 www.snom.com。检索于 2018-04-08。使用内核 Linux 的 GNU 操作系统的变体现在被广泛使用；尽管这些系统通常被称为“Linux”，但它们更准确地称为“GNU/Linux 系统”。
^Stallman, Richard (2007-06-19). "Linux and the GNU Project". About the GNU Project. Free Software Foundation. Retrieved 2007-07-22.^ 斯托曼，理查德 (2007-06-19)。 “Linux 和 GNU 项目”。关于 GNU 项目。自由软件基金会。检索于 2007-07-22。
^The Debian Project (2007-07-11). "What is Debian?". About Debian. Retrieved 2007-07-22.^ Debian 项目 (2007-07-11)。 “Debian 是什么？”。关于 Debian。检索于 2007-07-22。
^Nexenta Systems, Inc. (2007-06-20). "Unix Portal:Nexenta OS - Nexenta OpenSolaris". Sponsors & Support. Archived from the original on 2007-07-11. Retrieved 2007-07-22. This work is initiated and sponsored by Nexenta Systems, Inc. Technical support is available from a variety of sources, including Community and Web Forums.^ Nexenta 系统公司 (2007-06-20)。 “Unix 门户：Nexenta OS - Nexenta OpenSolaris”。赞助商和支持。原始存档于 2007-07-11。检索于 2007-07-22。这项工作由 Nexenta Systems, Inc. 发起和赞助。技术支持可从各种来源获得，包括社区和网络论坛。
GNU Guix System or Guix System[5][6] (previously GuixSD[7]) is a rolling release, free and open sourceLinux distribution built around the GNU Guixpackage manager.[8][9] It enables a declarative operating system configuration[10] and allows a reliable system upgrades which the user can rollback.[11] It uses the GNU Shepherd init system[12][13] and the Linux-libre kernel, with support for the GNU Hurd kernel under development.[14] On February 3, 2015, the Free Software Foundation added the distribution to its list of endorsed free Linux distributions.[15] The Guix package manager and the Guix System drew inspiration from and were based on the Nix package manager and NixOS respectively.[16]GNU Guix System 或 Guix System[5][6]（以前称为 GuixSD[7]）是一个围绕 GNU Guix 包管理器构建的滚动发布、免费和开源的 Linux 发行版。[8][9]它支持声明式操作系统配置[10]，并允许可靠的系统升级，用户可以回滚。[11]它使用 GNU Shepherd 初始化系统[12][13] 和 Linux-libre 内核，支持正在开发的 GNU Hurd 内核。 [14] 2015 年 2 月 3 日，自由软件基金会将该发行版添加到其认可的免费 Linux 发行版列表中。 [15] Guix 包管理器和 Guix 系统分别从 Nix 包管理器和 NixOS 中汲取灵感并基于它们。 [16]
System services, defined in Guile Scheme,[20] enable the user to declaratively compose the configuration of daemons and background services and specify configurations. This enables the user, within a single configuration file or modularized configuration, to configure the whole operating system (e.g., to have a tor proxy, an sshd server, and a webserver serving guix-web via NGINX on a specific port at bootup). They can:[21]Guile Scheme[20] 中定义的系统服务使用户能够以声明方式组合守护进程和后台服务的配置并指定配置。这使用户能够在单个配置文件或模块化配置中配置整个操作系统（例如，在启动时通过 NGINX 在特定端口上拥有 tor 代理、sshd 服务器和服务 guix-web 的网络服务器）。他们可以：[21]
generate files in the filesystem (needed by some applications e.g. files in /etc)在文件系统中生成文件（某些应用程序需要，例如 /etc 中的文件）
run any code for setting up daemons运行任何代码来设置守护进程
create specific user and group accounts (e.g. a database user for postgresql)创建特定的用户和组帐户（例如 postgresql 的数据库用户）
GNU Shepherd init system[edit]GNU Shepherd 初始化系统[编辑]
The Guix System uses the GNU Daemon Shepherd, formerly known as "dmd" ("Daemon managing Daemons"), as its init system, which is developed in tandem with Guix and is written and configurable in Guile.[22] It supplies user-space functionality asynchronously as services, which under Shepherd are generic functions and objectdata types which it uses to extend the base operating system in a defined way. In contrast to systemd, a userspace shepherd process runs as the user. Central to the Shepherd model of user space initialization is the concept of the extension, a form of composability whereby services are designed to be layered onto other services, augmenting them with more elaborate or specialised behaviours as desired.[23] This expresses the instantiation-based dependency relationships found in many modern init systems,[24] making the system modular, but also allows services to interact variadically with other services in arbitrary ways, e.g. a service which extends two other services, requiring only one to be present, but readily extending the second one if it is later instantiated without the need for any further reconfiguration or setup.
Guix 系统使用 GNU Daemon Shepherd，以前称为“dmd”（“Daemon managing Daemons”）作为它的 init 系统，它是与 Guix 一起开发的，在 Guile 中编写和配置。 [22]它以服务的形式异步提供用户空间功能，在 Shepherd 下，它是通用函数和对象数据类型，用于以定义的方式扩展基本操作系统。与 systemd 不同的是，用户空间的牧羊人进程以用户身份运行。用户空间初始化的 Shepherd 模型的核心是扩展的概念，这是一种可组合性形式，服务被设计为分层到其他服务上，根据需要用更精细或专门的行为来增强它们。 [23]这表达了在许多现代初始化系统中发现的基于实例化的依赖关系，[24] 使系统模块化，但也允许服务以任意方式与其他服务进行可变交互，例如一种扩展其他两个服务的服务，只需要一个存在，但如果稍后实例化，则可以轻松扩展第二个服务，而无需任何进一步的重新配置或设置。
Shepherd also provides virtual services which allow dynamic dispatch over a class of related service objects, such as all those which instantiate a mail transfer agent (MTA) for the system.[25] A system governed via the Shepherd daemon can represent its user space as a directed acyclic graph, with the "system-service," which is responsible for early phases of boot and init, as its root, and all subsequently initialized services as extensions to system-service functionality, either directly or transitively over other services.[23][26]Shepherd 还提供虚拟服务，允许动态调度一类相关服务对象，例如为系统实例化邮件传输代理 (MTA) 的所有对象。 [25]通过 Shepherd 守护进程管理的系统可以将其用户空间表示为有向无环图，其中“系统服务”负责引导和初始化的早期阶段，作为其根，所有随后初始化的服务作为系统的扩展-服务功能，直接或通过其他服务传递。[23][26]
It is intended to be highly programmable by the system administrator using Guile, but it can also be used to manage per-user profiles of unprivileged daemons and services.[27] Its services and configuration are stored uniformly as object-oriented Scheme code, and while a core set of services are provided with the basic Guix System,[28] arbitrary new services can be flexibly declared, and through Guile's object system, GOOPS, existing services can be redefined at the user's discretion by asking the Shepherd to dynamically rewrite services in specified ways on instantiation.[29][30]它旨在由系统管理员使用 Guile 进行高度编程，但它也可用于管理非特权守护进程和服务的每个用户配置文件。 [27]它的服务和配置统一存储为面向对象的Scheme代码，同时提供了一套核心服务与基本的Guix系统[28]，可以灵活声明任意新服务，并通过Guile的对象系统、GOOPS、现有服务可以由用户自行决定重新定义，方法是要求 Shepherd 在实例化时以指定方式动态重写服务。[29][30]
GNU Shepherd was originally designed to work with GNU Hurd, and was later adopted by Guix System.[31]GNU Shepherd 最初设计用于与 GNU Hurd 一起工作，后来被 Guix 系统采用。 [31]
To date, the Guix System is dependent on unstable git repository development[32] shared with Guix but enables users or organizations to set up stable release channels themselves via the channel-feature.[33]迄今为止，Guix 系统依赖于与 Guix 共享的不稳定 git 存储库开发[32]，但允许用户或组织通过通道功能自行设置稳定的发布通道。[33]
Packages in Guix are generally very up-to-date thanks to the lack of a package maintainer bottlenecks. Anyone can contribute an update subject to community approval and the process is assisted by tools such as guix refresh.[34]由于没有包维护瓶颈，Guix 中的包通常都是最新的。任何人都可以在社区批准的情况下贡献更新，并且该过程由 guix refresh 等工具协助。 [34]
Changes to the git repository are peer-reviewed by community members and committed by one of the 45 people with commit access.[35] In practice these builds sometimes cause system breakages for users because of a typo or similar error, but these are often solved within minutes. The way Guix pull operates means users retain a working system in the meantime.
对 git 存储库的更改由社区成员进行同行评审，并由 45 名具有提交权限的人之一提交。 [35]在实践中，这些构建有时会因为拼写错误或类似错误而导致用户系统崩溃，但这些问题通常会在几分钟内解决。 Guix pull 操作的方式意味着用户同时保留一个工作系统。
If a system update leaves users with a broken system, users can easily roll back individual packages as well as the whole system state.[36] This means that the kind of stable channel that is very common in other Linux distributions is no longer needed for users who are willing to report a bug and wait a few minutes, when trying to update via guix pull.
如果系统更新给用户留下了损坏的系统，用户可以轻松回滚单个软件包以及整个系统状态。 [36]这意味着在尝试通过 guix pull 更新时，对于愿意报告错误并等待几分钟的用户来说，不再需要在其他 Linux 发行版中非常常见的那种稳定渠道。
Jesse Smith from DistroWatch Weekly reviewed GNU Guix System 0.15.0 (at the time named GuixSD), and said, "GuixSD has a package manager that I like", but criticized the limited hardware support and its limited documentation.[37] The documentation has since then been expanded and improved with videos[38] and a cookbook[39] in six languages with tutorials, how-to guides and examples.
DistroWatch Weekly 的 Jesse Smith 评论了 GNU Guix System 0.15.0（当时名为 GuixSD），并说，“GuixSD 有一个我喜欢的包管理器”，但批评了有限的硬件支持和有限的文档。 [37]从那时起，该文档通过视频 [38] 和一本食谱 [39] 以六种语言进行了扩展和改进，其中包含教程、操作指南和示例。
^"Download — GNU Guix". Archived from the original on August 1, 2020. Retrieved November 3, 2019.^ “下载——GNU Guix”。原始存档于 2020 年 8 月 1 日。检索于 2019 年 11 月 3 日。
^"What to call Guix?" (Mailing list). gnu-system-discuss. January 15, 2015. Archived from the original on August 7, 2020. Retrieved August 3, 2020.^ “如何称呼 Guix？” （邮件列表）。 gnu 系统讨论。 2015 年 1 月 15 日。原始存档于 2020 年 8 月 7 日。检索于 2020 年 8 月 3 日。
^"Using the Configuration System". gnu.org. Archived from the original on April 29, 2019. Retrieved April 27, 2019.^ “使用配置系统”。 gnu.org。原始存档于 2019 年 4 月 29 日。2019 年 4 月 27 日检索。
^"Package Management". gnu.org. Archived from the original on May 21, 2019. Retrieved April 27, 2019.^ “包管理”。 gnu.org。原始存档于 2019 年 5 月 21 日。2019 年 4 月 27 日检索。
^"Download". gnu.org. Archived from the original on October 6, 2021. Retrieved October 6, 2021.^ “下载”。 gnu.org。原始存档于 2021 年 10 月 6 日。2021 年 10 月 6 日检索。
^Mathieu Othacehe. "Porting GuixSD to ARMv7". Archived from the original on December 25, 2017. Retrieved February 17, 2018.^ 马修·奥萨赫。 “将 GuixSD 移植到 ARMv7”。原始存档于 2017 年 12 月 25 日。2018 年 2 月 17 日检索。
^Marusich, Chris; Le Bouter, Léo (April 12, 2021). "New Supported Platform: powerpc64le-linux". Archived from the original on May 16, 2021. Retrieved October 6, 2021.^ Marusich, 克里斯; Le Bouter, Léo（2021 年 4 月 12 日）。 “新支持的平台：powerpc64le-linux”。原始存档于 2021 年 5 月 16 日。2021 年 10 月 6 日检索。
^"guix.git". git.savannah.gnu.org. Archived from the original on May 11, 2019. Retrieved May 11, 2019.^ “guix.git”。 git.savannah.gnu.org。原始存档于 2019 年 5 月 11 日。2019 年 5 月 11 日检索。
^"guix-devel mailing lists". Archived from the original on September 19, 2019. Retrieved November 5, 2016.^ “guix-devel 邮件列表”。原始存档于 2019 年 9 月 19 日。2016 年 11 月 5 日检索。
^"systemd: Unit Dependencies and Order". Fedora Magazine. November 25, 2015. Archived from the original on August 1, 2020. Retrieved November 5, 2016.^ “systemd：单元依赖关系和顺序”。 Fedora 杂志。 2015 年 11 月 25 日。原始存档于 2020 年 8 月 1 日。2016 年 11 月 5 日检索。
^"The GNU Shepherd Manual: Jump Start". GNU Project. Archived from the original on August 1, 2020. Retrieved November 5, 2016.^ “GNU 牧羊人手册：快速入门”。 GNU 项目。原始存档于 2020 年 8 月 1 日。2016 年 11 月 5 日检索。
^"The GNU Shepherd Manual". GNU Project. Archived from the original on August 1, 2020. Retrieved November 5, 2016.^ “GNU 牧羊人手册”。 GNU 项目。原始存档于 2020 年 8 月 1 日。2016 年 11 月 5 日检索。
^"GNU Guix Reference Manual: Services". GNU Project. Archived from the original on December 25, 2018. Retrieved November 5, 2016.^ “GNU Guix 参考手册：服务”。 GNU 项目。原始存档于 2018 年 12 月 25 日。2016 年 11 月 5 日检索。
^"GNU Shepherd". GNU project. Archived from the original on February 12, 2016. Retrieved February 12, 2016.^ “GNU 牧羊人”。 GNU 项目。原始存档于 2016 年 2 月 12 日。2016 年 2 月 12 日检索。
^"Re: We need an RFC procedure" (Mailing list). Archived from the original on August 1, 2020. Retrieved April 27, 2019.^ “回复：我们需要一个 RFC 程序”（邮件列表）。原始存档于 2020 年 8 月 1 日。2019 年 4 月 27 日检索。
^"Channels". gnu.org. Archived from the original on May 7, 2019. Retrieved April 27, 2019.^ “频道”。 gnu.org。原始存档于 2019 年 5 月 7 日。检索于 2019 年 4 月 27 日。
^"Invoking guix refresh". gnu.org. Archived from the original on December 26, 2018. Retrieved May 16, 2019.^ “调用 guix 刷新”。 gnu.org。原始存档于 2018 年 12 月 26 日。2019 年 5 月 16 日检索。
^"GNU Guix - Summary: Project Memberlist". gnu.org. Archived from the original on August 1, 2020. Retrieved April 27, 2019.^ “GNU Guix - 总结：项目成员列表”。 gnu.org。原始存档于 2020 年 8 月 1 日。2019 年 4 月 27 日检索。
^"Invoking guix system". gnu.org. Archived from the original on May 26, 2019. Retrieved April 27, 2019.^ “调用 guix 系统”。 gnu.org。原始存档于 2019 年 5 月 26 日。检索于 2019 年 4 月 27 日。
^Smith, Jesse. "Guix System Distribution 0.15.0 and ReactOS 0.4.9". distrowatch.com (778). Archived from the original on July 30, 2019. Retrieved August 30, 2018.^ 史密斯，杰西。 “Guix 系统分发版 0.15.0 和 ReactOS 0.4.9”。 distrowatch.com (778)。原始存档于 2019 年 7 月 30 日。检索于 2018 年 8 月 30 日。
^"Videos". Archived from the original on August 1, 2020. Retrieved March 3, 2020.^ “视频”。原始存档于 2020 年 8 月 1 日。2020 年 3 月 3 日检索。
^"Cookbook". Archived from the original on August 1, 2020. Retrieved March 3, 2020.^ “食谱”。原始存档于 2020 年 8 月 1 日。2020 年 3 月 3 日检索。
^"About — GuixSD". www.gnu.org. Archived from the original on December 27, 2015. Retrieved May 3, 2018.^ “关于——GuixSD”。 www.gnu.org。原始存档于 2015 年 12 月 27 日。2018 年 5 月 3 日检索。
Parabola GNU/Linux-libre is an operating system for the i686, x86-64 and ARMv7 architectures.[4] It is based on many of the packages from Arch Linux and Arch Linux ARM,[3] but distinguishes from the former by offering only free software. It includes the GNU operating system components common to many Linux distributions and the Linux-libre kernel instead of the generic Linux kernel.[4] Parabola is listed by the Free Software Foundation as a completely free operating system, true to their Free System Distribution Guidelines.[5][6]Parabola GNU/Linux-libre 是一个适用于 i686、x86-64 和 ARMv7 架构的操作系统。 [4]它基于 Arch Linux 和 Arch Linux ARM 的许多软件包，[3] 但与前者的区别在于仅提供免费软件。它包括许多 Linux 发行版通用的 GNU 操作系统组件和 Linux-libre 内核，而不是通用的 Linux 内核。 [4] Parabola 被自由软件基金会列为完全自由的操作系统，符合他们的自由系统分发指南。[5][6]
Parabola uses a rolling release model like Arch, such that a regular system update is all that is needed to obtain the latest software. Development focuses on system simplicity, community involvement and use of the latest free software packages.
Parabola 使用像 Arch 一样的滚动发布模型，因此只需定期更新系统即可获得最新的软件。开发侧重于系统简单性、社区参与和最新免费软件包的使用。
Parabola was originally proposed by members of the gNewSenseIRC channel in 2009. Members of different Arch Linux communities, especially Spanish-speaking members, started the development and maintenance of the project software and documentation.[7]Parabola 最初由 gNewSense IRC 频道的成员于 2009 年提出。不同 Arch Linux 社区的成员，尤其是西班牙语成员开始了该项目软件和文档的开发和维护。[7]
On May 20, 2011, the Parabola distribution was recognized as a completely free project by GNU, making it part of the FSF list of free distributions.[8]2011 年 5 月 20 日，Parabola 发行版被 GNU 认可为完全免费的项目，使其成为 FSF 免费发行版列表的一部分。 [8]
In February 2012 Dmitrij D. Czarkoff reviewed Parabola for OSNews. Czarkoff reported that on his test computer a number of hardware problems surfaced, due to lack of free firmware. He said
2012 年 2 月，Dmitrij D. Czarkoff 为 OSNews 评论了 Parabola。 Czarkoff 报告说，由于缺少免费固件，他的测试计算机出现了一些硬件问题。他说
That effectively means that many devices are not supported in Parabola. Eg., after installing it on my Acer Aspire One 531h netbook I couldn't use my Broadcom bluetooth module and Intel's WiFi/WiMax Link 5150 adapter. (I still could use my HTC Magic with a custom Gingerbread ROM as a USB 3G/WiFi modem, though having something always connected to USB port is pretty annoying on laptop and specifically on netbook.)这实际上意味着 Parabola 不支持许多设备。例如，在我的 Acer Aspire One 531h 上网本上安装它后，我无法使用我的 Broadcom 蓝牙模块和英特尔的 WiFi/WiMax Link 5150 适配器。 （我仍然可以将我的 HTC Magic 与自定义 Gingerbread ROM 用作 USB 3G/WiFi 调制解调器，尽管总是将某些东西连接到 USB 端口在笔记本电脑上非常烦人，尤其是在上网本上。）
— Dmitrij D. Czarkoff—>德米特里·D·查尔科夫
Czarkoff also criticized the lack of documentation available for Parabola. He concluded "The overall impression of the Parabola GNU/Linux user experience exactly matches the one of Arch: a system with easy and flexible installation and configuration process and good choice of free software packages. Though the lack of documentation spoils the user experience, the Arch Linux resources can be used to further configure and extend the distribution. If my hardware would allow, I would probably stick with Parabola."[9][10]Czarkoff 还批评了 Parabola 缺乏可用的文档。他总结道：“Parabola GNU/Linux 用户体验的总体印象与 Arch 完全一致：一个安装和配置过程简单灵活的系统，以及免费软件包的不错选择。虽然缺乏文档会破坏用户体验，但Arch Linux 资源可用于进一步配置和扩展发行版。如果我的硬件允许，我可能会坚持使用 Parabola。”[9][10]
Parabola used to have a mips64el port to provide support for the Chinese Loongson processor used in the Lemote Yeeloong laptop. It was discontinued due to a lack of resources and interest, and the final activity was seen in July 2014.[11]Parabola 曾经有一个 mips64el 端口来为 Lemote Yeeloong 笔记本电脑中使用的中国龙芯处理器提供支持。由于缺乏资源和兴趣而停止，最终活动出现在 2014 年 7 月。 [11]
Robert Rijkhoff reviewed Parabola GNU/Linux for DistroWatch in September 2017.[12]Robert Rijkhoff 于 2017 年 9 月为 DistroWatch 审查了 Parabola GNU/Linux。 [12]
Differences from Arch and Arch ARM[edit]与 Arch 和 Arch ARM 的区别[编辑]
The project uses only 100% free software from the official Arch repositories for the i686 and x86-64 architectures and official Arch ARM repositories (except [alarm] and [aur]) for the ARMv7. It uses free replacements when possible, such as the Linux-libre kernel instead of the generic Linux kernel.
该项目仅使用来自 i686 和 x86-64 架构的官方 Arch 存储库和 ARMv7 的官方 Arch ARM 存储库（[alarm] 和 [aur] 除外）的 100% 免费软件。它尽可能使用免费替换，例如 Linux-libre 内核而不是通用 Linux 内核。
The filtering process removes around 700 software packages from the repositories that do not meet the requirements of the Free Software Definition for each architecture.[13]过滤过程从存储库中删除了大约 700 个不符合每个体系结构的自由软件定义要求的软件包。 [13]
Parabola has established a social contract. The Parabola Social Contract commits the project to the free software community (viewing itself as only competing against nonfree systems), free culture, democracy, and to follow Arch's philosophy.[14] Under the covenant are included the GNU Free System Distribution Guidelines.
抛物线建立了社会契约。抛物线社会契约将项目提交给自由软件社区（将自己视为仅与非自由系统竞争）、自由文化、民主，并遵循 Arch 的哲学。 [14]盟约包括 GNU 自由系统分发指南。
There are two ways to install Parabola, either from scratch using installable ISO images, or by migrating from an existing Arch-based system. The latter process is almost as simple as switching to the Parabola repositories list.[2][15]有两种安装 Parabola 的方法，一种是使用可安装的 ISO 映像从头开始，另一种是从现有的基于 Arch 的系统迁移。后一个过程几乎与切换到 Parabola 存储库列表一样简单。[2][15]
TalkingParabola is a derivative install CD based on TalkingArch. It is a respin of the Parabola ISO modified to include speech and braille output for blind and visually impaired users. TalkingParabola retains all the features of the Parabola live image, but adds speech and braille packages to make it possible for blind and visually impaired users to install Parabola eyes-free.[16]TalkingParabola 是基于TalkingArch 的衍生安装光盘。它是 Parabola ISO 的重制版，经过修改以包括针对盲人和视障用户的语音和盲文输出。 TalkingParabola 保留了 Parabola 实时图像的所有功能，但添加了语音和盲文包，使盲人和视力受损的用户可以免视安装 Parabola。[16]
The Parabola community has created a number of cartoon characters for the project. The characters are a gnu and a cat named "Bola", who is conceived after Parabola's main characteristics: "elegant, minimalist and lightweight".[17]Parabola 社区为该项目创建了许多卡通人物。角色是一只牛羚和一只名叫“Bola”的猫，它是根据 Parabola 的主要特征构想出来的：“优雅、简约和轻便”。[17]
^"Parabola has a new mascot called Bola". Parabola project. April 2016. Retrieved 30 April 2016.^ “Parabola 有一个新的吉祥物叫做 Bola”。抛物线项目。 2016 年 4 月。2016 年 4 月 30 日检索。
The Arch Hurd project was founded on an Arch Linux forum thread[2] in January 2010 and, after a few weeks with many contributions, progressed to the point where it could boot in a virtual machine.[3] It aims to provide an Arch-like user environment (BSD-style init scripts, i686-optimised packages, use of the pacman package manager, rolling-release, and a KISS set up) on the Hurd which is stable enough for use.[1]Arch Hurd 项目于 2010 年 1 月在 Arch Linux 论坛线程 [2] 上成立，经过几周的大量贡献，它已经发展到可以在虚拟机中启动的程度。 [3]它旨在在 Hurd 上提供一个类似 Arch 的用户环境（BSD 风格的初始化脚本、i686 优化的包、pacman 包管理器的使用、滚动发布和 KISS 设置），它足够稳定以供使用。 [ 1]
As of April 2021, the official packages were last updated in May 2019.[4]截至 2021 年 4 月，官方软件包的最后更新时间为 2019 年 5 月。[4]
Despite having a small development team,[5] much progress has been made since its founding, such as booting on real hardware,[6] packaging everything for a basic web server,[7] and the production of an unofficial graphical LiveCD.[8][9][10]尽管拥有一个小型开发团队，[5] 自成立以来已经取得了很大进展，例如在真实硬件上启动，[6] 为基本 Web 服务器打包所有内容，[7] 以及非官方图形 LiveCD 的制作。[ 8][9][10]
In June 2011, Arch Hurd announced successful integration of Device Driver Environment (DDE) — the framework for Linux drivers on Hurd, which improves the network hardware support in the distribution and makes it nearly usable.[11]2011 年 6 月，Arch Hurd 宣布成功集成设备驱动程序环境 (DDE)——Hurd 上的 Linux 驱动程序框架，改进了发行版中的网络硬件支持并使其几乎可用。 [11]
^ Jump up to: ab"About", Arch Hurd, archived from the original on 2011-01-08, retrieved 2011-01-18^ 跳转至： a b "About", Arch Hurd，自原文存档于 2011-01-08，检索于 2011-01-18
^"Arch Hurd Project", Arch Linux Forums, 2010-01-04, retrieved 2011-01-18^ “Arch Hurd 项目”，Arch Linux 论坛，2010-01-04，2011-01-18 检索
^Vervloesem, Koen (2010-07-07). "The Hurd: GNU's quest for the perfect kernel". LWN.net. Hurd distributions. Retrieved 2011-12-08.^ Vervloesem, Koen (2010-07-07)。 “The Hurd：GNU 对完美内核的追求”。 LWN.net。赫德分布。检索于 2011-12-08。
^
Gilles, Stephen (2011-06-29), "Successful use of DDE!", Arch Hurd, archived from the original on 2012-02-23, retrieved 2011-12-08^ Gilles, Stephen (2011-06-29), "Successful use of DDE!", Arch Hurd, archived from the original on 2012-02-23, 检索 2011-12-08
Debian (/ˈdɛbiən/),[6][7] also known as Debian GNU/Linux, is a Linux distribution composed of free and open-source software, developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993,[8] and its first stable version (1.1) was released on June 17, 1996.[9] The Debian Stable branch is the most popular edition for personal computers and servers. Debian is also the basis for many other distributions, most notably Ubuntu.
Debian (/ˈdɛbiən/),[6][7] 也称为 Debian GNU/Linux，是由自由和开源软件组成的 Linux 发行版，由社区支持的 Debian 项目开发，该项目由 Ian Murdock 于1993 年 8 月 16 日。 Debian 的第一个版本 (0.01) 于 1993 年 9 月 15 日发布，[8] 其第一个稳定版本 (1.1) 于 1996 年 6 月 17 日发布。 [9] Debian Stable 分支是最流行的个人计算机和服务器版本。 Debian 也是许多其他发行版的基础，最著名的是 Ubuntu。
Debian is one of the oldest operating systems based on the Linux kernel. The project is coordinated over the Internet by a team of volunteers guided by the Debian Project Leader and three foundational documents: the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. New distributions are updated continually, and the next candidate is released after a time-based freeze.
Debian 是基于 Linux 内核的最古老的操作系统之一。该项目由一个志愿者团队通过互联网协调，该团队由 Debian 项目负责人和三个基础文件指导：Debian 社会契约、Debian 宪法和 Debian 自由软件指南。新发行版不断更新，下一个候选版本在基于时间的冻结后发布。
Since its founding, Debian has been developed openly and distributed freely according to the principles of the GNU Project. Because of this, the Free Software Foundation sponsored the project from November 1994 to November 1995. When the sponsorship ended, the Debian Project formed the nonprofit organizationSoftware in the Public Interest to continue financially supporting development.
自成立以来，Debian 一直根据 GNU 项目的原则进行公开开发和自由发布。正因为如此，自由软件基金会从 1994 年 11 月到 1995 年 11 月赞助了该项目。赞助结束后，Debian 项目成立了非营利组织 Software in the Public Interest 以继续为开发提供资金支持。
Debian distribution codenames are based on the names of characters from the Toy Story films. Debian's unstable trunk is named after Sid, a character who regularly destroyed his toys.[10]Debian 发行代号是基于玩具总动员电影中人物的名字。 Debian 的不稳定主干以 Sid 命名，Sid 是一个经常毁坏他的玩具的角色。 [10]
Debian was first announced on August 16, 1993, by Ian Murdock, who initially called the system "the Debian Linux Release".[11][12] The word "Debian" was formed as a portmanteau of the first name of his then-girlfriend (later ex-wife) Debra Lynn and his own first name.[13] Before Debian's release, the Softlanding Linux System (SLS) had been a popular Linux distribution and the basis for Slackware.[14] The perceived poor maintenance and prevalence of bugs in SLS motivated Murdock to launch a new distribution.[15]Debian 于 1993 年 8 月 16 日由 Ian Murdock 首次发布，他最初称该系统为“Debian Linux Release”。[11][12] “Debian”这个词是他当时的女友（后来的前妻）Debra Lynn 的名字和他自己的名字的合成词。 [13]在 Debian 发布之前，Softlanding Linux System (SLS) 是一个流行的 Linux 发行版，也是 Slackware 的基础。 [14] SLS 中明显的维护不善和错误普遍存在促使 Murdock 推出新的发行版。 [15]
Debian 0.01, released on September 15, 1993, was the first of several internal releases.[8] Version 0.90 was the first public release,[8] providing support through mailing lists hosted at Pixar.[16] The release included the Debian Linux Manifesto, outlining Murdock's view for the new operating system. In it he called for the creation of a distribution to be maintained "openly in the spirit of Linux and GNU."[17]Debian 0.01 于 1993 年 9 月 15 日发布，是多个内部版本中的第一个。 [8] 0.90 版是第一个公开版本，[8] 通过 Pixar 托管的邮件列表提供支持。 [16]该版本包括 Debian Linux 宣言，概述了 Murdock 对新操作系统的看法。在其中，他呼吁创建一个“本着 Linux 和 GNU 的精神公开维护”的发行版。[17]
The Debian project released the 0.9x versions in 1994 and 1995.[18] During this time it was sponsored by the Free Software Foundation for one year.[19] Ian Murdock delegated the base system, the core packages of Debian, to Bruce Perens and Murdock focused on the management of the growing project.[15] The first ports to non-IA-32 architectures began in 1995, and Debian 1.1 was released in 1996.[20] By that time and thanks to Ian Jackson, the dpkg package manager was already an essential part of Debian.[21]Debian 项目在 1994 年和 1995 年发布了 0.9x 版本。 [18]在此期间，它由自由软件基金会赞助了一年。 [19] Ian Murdock 将 Debian 的基础系统、核心软件包委托给了 Bruce Perens，而 Murdock 则专注于管理不断发展的项目。 [15]第一个非 IA-32 架构的移植始于 1995 年，Debian 1.1 于 1996 年发布。 [20]到那个时候，感谢 Ian Jackson，dpkg 包管理器已经成为 Debian 的重要组成部分。 [21]
In 1996, Bruce Perens assumed the project leadership. Perens was a controversial leader, regarded as authoritarian and strongly attached to Debian.[22] He drafted a social contract and edited suggestions from a month-long discussion into the Debian Social Contract and the Debian Free Software Guidelines.[23] After the FSF withdrew their sponsorship in the midst of the free software vs. open source debate,[24] Perens initiated the creation of the legal umbrella organizationSoftware in the Public Interest instead of seeking renewed involvement with the FSF.[20] He led the conversion of the project from a.out to ELF.[15] He created the BusyBox program to make it possible to run a Debian installer on a single floppy disk, and wrote a new installer.[25] By the time Debian 1.2 was released, the project had grown to nearly two hundred volunteers.[15] Perens left the project in 1998.[26]1996 年，Bruce Perens 担任项目领导。 Perens 是一位有争议的领导者，被认为是专制的并且强烈依附于 Debian。 [22]他起草了一份社会契约，并将长达一个月的讨论中的建议编辑成 Debian 社会契约和 Debian 自由软件指南。 [23]在 FSF 在自由软件与开源辩论中撤回赞助后，[24] Perens 开始创建合法的保护性组织 Software in the Public Interest，而不是寻求重新参与 FSF。 [20]他领导了项目从 a.out 到 ELF 的转换。 [15]他创建了 BusyBox 程序，使在一张软盘上运行 Debian 安装程序成为可能，并编写了一个新的安装程序。 [25]到 Debian 1.2 发布时，该项目已经发展到近 200 名志愿者。 [15] Perens 于 1998 年离开了该项目。 [26]
Ian Jackson became the leader in 1998.[27] Debian 2.0 introduced the second official port, m68k.[18] During this time the first port to a non-Linux kernel, Debian GNU/Hurd, was started.[28] On December 2, the first Debian Constitution was ratified.[29]伊恩·杰克逊于 1998 年成为领袖。 [27] Debian 2.0 引入了第二个官方端口，m68k。[18]在此期间，第一个非 Linux 内核 Debian GNU/Hurd 的移植开始了。 [28] 12 月 2 日，第一部 Debian 章程获得批准。 [29]
From 1999, the project leader was elected yearly.[30] The Advanced Packaging Tool was deployed with Debian 2.1.[18] The number of applicants was overwhelming and the project established the new member process.[31][32] The first Debian derivatives, namely Libranet,[33]Corel Linux and Stormix's Storm Linux, were started in 1999.[20] The 2.2 release in 2000 was dedicated to Joel Klecker, a developer who died of Duchenne muscular dystrophy.[34]从1999年起，每年选举项目负责人[30]。 Advanced Packaging Tool 与 Debian 2.1 一起部署。[18]申请者人数众多，该项目建立了新的成员流程。[31][32]第一个 Debian 衍生产品，即 Libranet、[33] Corel Linux 和 Stormix 的 Storm Linux，于 1999 年启动。 [20] 2000 年的 2.2 版本是献给 Joel Klecker 的，他是一位死于 Duchenne 肌营养不良症的开发人员。 [34]
In late 2000, the project reorganized the archive with new package "pools" and created the Testing distribution, made up of packages considered stable, to reduce the freeze for the next release.[20] In the same year, developers began holding an annual conference called DebConf with talks and workshops for developers and technical users.[35] In May 2001, Hewlett-Packard announced plans to base its Linux development on Debian.[36]在 2000 年底，该项目用新的包“池”重组了档案，并创建了测试发行版，由被认为稳定的包组成，以减少下一个版本的冻结。 [20]同年，开发人员开始举办名为 DebConf 的年度会议，为开发人员和技术用户举办讲座和研讨会。 [35] 2001 年 5 月，惠普宣布计划将其 Linux 开发基于 Debian。 [36]
In July 2002, the project released version 3.0, code-named Woody, the first release to include cryptographic software, a free licensed KDE and internationalization.[37] During these last release cycles, the Debian project drew considerable criticism from the free software community because of the long time between stable releases.[38][39][40]2002 年 7 月，该项目发布了代号为 Woody 的 3.0 版，这是第一个包含加密软件、免费许可的 KDE 和国际化版本的版本。 [37]在最近的这些发布周期中，Debian 项目因稳定版本之间的间隔时间过长而受到自由软件社区的大量批评。 [38][39][40]
Some events disturbed the project while working on Sarge, as Debian servers were attacked by fire and hackers.[20][41] One of the most memorable was the Vancouver prospectus.[42][43][44] After a meeting held in Vancouver, release manager Steve Langasek announced a plan to reduce the number of supported ports to four in order to shorten future release cycles.[45] There was a large reaction because the proposal looked more like a decision and because such a drop would damage Debian's aim to be "the universal operating system".[46][47][48]在 Sarge 上工作时，一些事件扰乱了项目，因为 Debian 服务器遭到火灾和黑客攻击。 [20][41]最令人难忘的是温哥华招股说明书。 [42][43][44]在温哥华召开会议后，发布经理 Steve Langasek 宣布了一项计划，将支持的端口数量减少到四个，以缩短未来的发布周期。 [45]由于提案看起来更像是一个决定，而且这样的放弃会损害 Debian 成为“通用操作系统”的目标，因此引起了很大的反响。[46][47][48]
The first version of the Debian-based Ubuntu, named "4.10 Warty Warthog", was released on October 20, 2004.[49] Because it was distributed as a free download, it became one of the most popular and successful operating systems with more than "40 million users" according to Canonical Ltd.[50][51] However, Murdock was critical of the differences between Ubuntu packages and Debian, stating that it leads to incompatibilities.[52]基于 Debian 的 Ubuntu 的第一个版本，名为“4.10 Warty Warthog”，于 2004 年 10 月 20 日发布。 [49]根据 Canonical Ltd. 的说法，由于它是作为免费下载分发的，它成为最受欢迎和最成功的操作系统之一，拥有超过“4000 万用户”[50][51]然而，默多克对 Ubuntu 软件包和 Debian 之间的差异持批评态度，指出这会导致不兼容。 [52]
Sarge and later releases (2005–present)[edit]Sarge 及后续版本（2005 年至今）[编辑]
Debian 4 (Etch), 2007Debian 4（蚀刻），2007
The 3.1 Sarge release was made in June 2005. This release updated 73% of the software and included over 9,000 new packages. A new installer with a modular design, Debian-Installer, allowed installations with RAID, XFS and LVM support, improved hardware detection, made installations easier for novice users, and was translated into almost forty languages. An installation manual and release notes were in ten and fifteen languages respectively. The efforts of Skolelinux, Debian-Med and Debian-Accessibility raised the number of packages that were educational, had a medical affiliation, and ones made for people with disabilities.[20][53]3.1 Sarge 版本于 2005 年 6 月发布。此版本更新了 73% 的软件并包括 9,000 多个新软件包。具有模块化设计的新安装程序 Debian-Installer 允许安装 RAID、XFS 和 LVM 支持，改进了硬件检测，使新手用户更容易安装，并被翻译成近 40 种语言。安装手册和发行说明分别以十种和十五种语言提供。 Skolelinux、Debian-Med 和 Debian-Accessibility 的努力增加了具有教育意义、具有医学背景以及为残障人士制作的软件包的数量。[20][53]
In 2006, as a result of a much-publicized dispute, Mozilla software was rebranded in Debian, with Firefox forked as Iceweasel and Thunderbird as Icedove. The Mozilla Corporation stated that software with unapproved modifications could not be distributed under the Firefox trademark. Two reasons that Debian modifies the Firefox software are to change the non-free artwork and to provide security patches.[54][55] In February 2016, it was announced that Mozilla and Debian had reached an agreement and Iceweasel would revert to the name Firefox; similar agreement was anticipated for Icedove/Thunderbird.[56]2006 年，由于一场广为人知的争论，Mozilla 软件在 Debian 中更名，Firefox 分叉为 Iceweasel，Thunderbird 分叉为 Icedove。 Mozilla 公司声明未经批准修改的软件不能在 Firefox 商标下分发。 Debian 修改 Firefox 软件的两个原因是改变非自由的艺术作品和提供安全补丁。[54][55] 2016年2月，宣布Mozilla与Debian达成协议，Iceweasel恢复名称为Firefox；预计 Icedove/Thunderbird 也将达成类似的协议。 [56]
A fund-raising experiment, Dunc-Tank, was created to solve the release cycle problem and release managers were paid to work full-time;[57] in response, unpaid developers slowed down their work and the release was delayed.[58]筹款实验 Dunc-Tank 的创建是为了解决发布周期问题，发布经理获得报酬以全职工作；[57] 作为回应，无报酬的开发人员放慢了他们的工作并延迟了发布。 [58]
Debian 4.0 (Etch) was released in April 2007, featuring the x86-64 port and a graphical installer.[18]Debian 4.0 (Etch) 于 2007 年 4 月发布，具有 x86-64 端口和图形安装程序。 [18]
Debian 5.0 (Lenny) was released in February 2009, supporting Marvell's Orion platform and netbooks such as the Asus Eee PC.[59] The release was dedicated to Thiemo Seufer, a developer who died in a car crash.[60]Debian 5.0 (Lenny) 于 2009 年 2 月发布，支持 Marvell 的 Orion 平台和上网本，例如 Asus Eee PC。 [59]该版本是献给死于车祸的开发人员 Thiemo Seufer 的。 [60]
Debian 6 (Squeeze), 2011Debian 6（挤压），2011
In July 2009, the policy of time-based development freezes on a two-year cycle was announced. Time-based freezes are intended to blend the predictability of time based releases with Debian's policy of feature based releases, and to reduce overall freeze time.[61] The Squeeze cycle was going to be especially short; however, this initial schedule was abandoned.[62] In September 2010, the backports service became official, providing more recent versions of some software for the stable release.[63]2009年7月，时基开发冻结两年一个周期的政策出台。基于时间的冻结旨在将基于时间的发布的可预测性与 Debian 基于特性的发布策略相结合，并减少整体冻结时间。 [61]挤压周期将特别短；然而，这个最初的时间表被放弃了。 [62] 2010 年 9 月，向后移植服务正式上线，为稳定版提供了一些软件的最新版本。 [63]
Debian 6.0 (Squeeze) was released in February 2011, featuring Debian GNU/kFreeBSD as a technology preview, along with adding a dependency-based boot system, and moving problematic firmware to the non-free section.[64]Debian 6.0 (Squeeze) 于 2011 年 2 月发布，以 Debian GNU/kFreeBSD 作为技术预览，同时添加了基于依赖项的引导系统，并将有问题的固件移至非自由部分。 [64]
Debian 7.0 (Wheezy) was released in May 2013, featuring multiarch support.[65]Debian 7.0 (Wheezy) 于 2013 年 5 月发布，具有多架构支持。 [65]
Debian 8.0 (Jessie) was released in April 2015, using systemd as the new init system.[66]Debian 8.0 (Jessie) 于 2015 年 4 月发布，使用 systemd 作为新的初始化系统。 [66]
Debian 9.0 (Stretch) was released in June 2017, with nftables as a replacement for iptables, support for Flatpak apps, and MariaDB as the replacement for MySQL.[67][68]Debian 9.0 (Stretch) 于 2017 年 6 月发布，nftables 作为 iptables 的替代品，支持 Flatpak 应用程序，MariaDB 作为 MySQL 的替代品。[67][68]
Debian 10.0 (Buster) was released in July 2019, adding support for Secure Boot and enabling AppArmor by default.[69]Debian 10.0 (Buster) 于 2019 年 7 月发布，增加了对安全启动的支持并默认启用 AppArmor。 [69]
Debian 11.0 (Bullseye) was released in August 2021, enabling persistency in the system journal, adding support for driverless scanning, and containing kernel-level support for exFAT filesystems.[70]Debian 11.0 (Bullseye) 于 2021 年 8 月发布，启用了系统日志的持久性，增加了对无驱动程序扫描的支持，并包含对 exFAT 文件系统的内核级支持。 [70]
Debian is still in development and new packages are uploaded to unstable every day.[71]Debian 仍在开发中，每天都有新的软件包上传到 unstable。 [71]
Debian used to be released as a very large set of CDs for each architecture, but with the release of Debian 9 (Stretch) in 2017, these have been dropped.[72]Debian 过去曾作为每个架构的大量 CD 发布，但随着 2017 年 Debian 9 (Stretch) 的发布，这些已被删除。 [72]
Throughout Debian's lifetime, both the Debian distribution and its website have won various awards from different organizations,[73] including Server Distribution of the Year 2011,[74]The best Linux distro of 2011,[75] and a Best of the Net award for October 1998.[76]在 Debian 的整个生命周期中，Debian 发行版及其网站都赢得了来自不同组织的各种奖项，[73] 包括 2011 年度服务器发行版、[74] 2011 年最佳 Linux 发行版、[75] 和网络最佳奖1998 年 10 月 [76]
On December 2, 2015, Microsoft announced that they would offer Debian GNU/Linux as an endorsed distribution on the Azure cloud platform.[77][78] Microsoft has also added a user environment to their Windows 10 desktop operating system called Windows Subsystem for Linux that offers a Debian subset.[79]2015 年 12 月 2 日，微软宣布他们将提供 Debian GNU/Linux 作为 Azure 云平台上的认可发行版。[77][78]微软还在他们的 Windows 10 桌面操作系统中添加了一个用户环境，称为 Windows Subsystem for Linux，它提供了一个 Debian 子集。 [79]
Graphical version of the debian Installerdebian 安装程序的图形版本
debian 10 console login and welcome messagedebian 10 控制台登录和欢迎消息
Debian has access to online repositories that contain over 51,000 packages.[80] Debian officially contains only free software, but non-free software can be downloaded and installed from the Debian repositories.[81] Debian includes popular free programs such as LibreOffice,[82]Firefox web browser, Evolution mail, K3b disc burner, VLC media player, GIMP image editor, and Evince document viewer.[81] Debian is a popular choice for servers, for example as the operating system component of a LAMP stack.[83][84]Debian 可以访问包含超过 51,000 个软件包的在线存储库。 [80] Debian 官方只包含自由软件，但可以从 Debian 存储库下载和安装非自由软件。 [81] Debian 包括流行的免费程序，例如 LibreOffice、[82] Firefox 网络浏览器、Evolution 邮件、K3b 光盘刻录机、VLC 媒体播放器、GIMP 图像编辑器和 Evince 文档查看器。 [81] Debian 是服务器的流行选择，例如作为 LAMP 堆栈的操作系统组件。[83][84]
Several flavors of the Linux kernel exist for each port. For example, the i386 port has flavors for IA-32 PCs supporting Physical Address Extension and real-time computing, for older PCs, and for x86-64 PCs.[85] The Linux kernel does not officially contain firmware lacking source code, although such firmware is available in non-free packages and alternative installation media.[86][87]每个端口都存在多种 Linux 内核版本。例如，i386 端口具有适用于支持物理地址扩展和实时计算的 IA-32 PC、旧 PC 和 x86-64 PC 的风格。 [85] Linux 内核并不正式包含缺少源代码的固件，尽管此类固件在非自由软件包和替代安装媒体中可用。[86][87]
XFCE is default on CD images and non-Linux portsXFCE 在 CD 映像和非 Linux 端口上是默认的
Debian offers CD and DVD images specifically built for XFCE, GNOME, KDE, MATE, Cinnamon, LXDE, and LXQT.[64]MATE is officially supported,[88] while Cinnamon support was added with Debian 8.0 Jessie.[89] Less common window managers such as Enlightenment, Openbox, Fluxbox, IceWM, Window Maker and others are available.[90]Debian 提供专门为 XFCE、GNOME、KDE、MATE、Cinnamon、LXDE 和 LXQT 构建的 CD 和 DVD 映像。 [64] MATE 得到官方支持，[88] 而 Debian 8.0 Jessie 添加了 Cinnamon 支持。 [89]不太常见的窗口管理器可用，例如 Enlightenment、Openbox、Fluxbox、IceWM、Window Maker 等。 [90]
The default desktop environment of version 7.0 Wheezy was temporarily switched to Xfce, because GNOME 3 did not fit on the first CD of the set.[91] The default for the version 8.0 Jessie was changed again to Xfce in November 2013,[92] and back to GNOME in September 2014.[93]7.0 版 Wheezy 的默认桌面环境暂时切换为 Xfce，因为 GNOME 3 不适合该套装的第一张 CD。 [91] 2013 年 11 月，Jessie 8.0 版的默认设置再次更改为 Xfce，[92] 并于 2014 年 9 月恢复为 GNOME。 [93]
Several parts of Debian are translated into languages other than American English, including package descriptions, configuration messages, documentation and the website.[94] The level of software localization depends on the language, ranging from the highly supported German and French to the barely translated Creek and Samoan.[95] The Debian 10 installer is available in 76 languages.[96]Debian 的几个部分被翻译成美式英语以外的语言，包括软件包描述、配置消息、文档和网站。 [94]软件本地化的水平取决于语言，从高度支持的德语和法语到几乎没有翻译的克里克语和萨摩亚语。 [95] Debian 10 安装程序支持 76 种语言。 [96]
Multimedia support has been problematic in Debian regarding codecs threatened by possible patent infringements, lacking source code, or under too restrictive licenses.[97] Even though packages with problems related to their distribution could go into the non-free area, software such as libdvdcss is not hosted at Debian .[98]多媒体支持在 Debian 中一直存在问题，因为编解码器受到可能的专利侵权、缺乏源代码或过于严格的许可的威胁。 [97]即使存在与分发相关的问题的软件包可以进入非自由区，像 libdvdcss 这样的软件也没有托管在 Debian 上。 [98]
A notable third party repository exists, formerly named Debian-multimedia.org,[99][100][101] providing software not present in debian such as Windows codecs, libdvdcss and the Adobe Flash Player.[102] Even though this repository is maintained by Christian Marillat, a debian developer, it is not part of the project and is not hosted on a debian server. The repository provides packages already included in debian, interfering with the official maintenance. Eventually, project leader Stefano Zacchiroli asked Marillat to either settle an agreement about the packaging or to stop using the "debian" name.[103] Marillat chose the latter and renamed the repository to deb-multimedia.org. The repository was so popular that the switchover was announced by the official blog of the debian project.[104]存在一个著名的第三方存储库，以前名为 Debian-multimedia.org，[99][100][101] 提供 debian 中不存在的软件，例如 Windows 编解码器、libdvdcss 和 Adobe Flash Player。[102]尽管这个存储库由 debian 开发人员 Christian Marillat 维护，但它不是项目的一部分，也不托管在 debian 服务器上。存储库提供了 debian 中已经包含的软件包，干扰了官方维护。最终，项目负责人 Stefano Zacchiroli 要求 Marillat 要么就包装达成协议，要么停止使用“debian”名称。 [103] Marillat 选择了后者并将存储库重命名为 deb-multimedia.org。该存储库非常受欢迎，以至于 debian 项目的官方博客宣布了切换。 [104]
Debian offers DVD and CD images for installation that can be downloaded using BitTorrent or jigdo. Physical discs can also be bought from retailers.[105] The full sets are made up of several discs (the amd64 port consists of 13 DVDs or 84 CDs),[106] but only the first disc is required for installation, as the installer can retrieve software not contained in the first disc image from online repositories.[107]Debian 提供用于安装的 DVD 和 CD 映像，可以使用 BitTorrent 或 jigdo 下载。物理光盘也可以从零售商处购买。 [105]全套由几张光盘组成（amd64 端口由 13 张 DVD 或 84 张 CD 组成），[106] 但安装只需要第一张光盘，因为安装程序可以从网上检索第一张光盘映像中不包含的软件资料库[107]
Debian offers different network installation methods. A minimal install of Debian is available via the netinst CD, whereby Debian is installed with just a base and later added software can be downloaded from the Internet. Another option is to boot the installer from the network.[108]Debian 提供不同的网络安装方法。 Debian 的最小安装可通过 netinst CD 获得，其中 Debian 只安装了一个基础，以后添加的软件可以从 Internet 下载。另一种选择是从网络引导安装程序。 [108]
The default bootstrap loader is GNU GRUB version 2, though the package name is simply grub, while version 1 was renamed to grub-legacy. This conflicts with (e.g., Fedora Linux), where grub version 2 is named grub2.
默认引导加载程序是 GNU GRUB 版本 2，尽管包名称只是 grub，而版本 1 已重命名为 grub-legacy。这与（例如 Fedora Linux）冲突，其中 grub 版本 2 被命名为 grub2。
The default desktop may be chosen from the DVD boot menu among GNOME, KDE Plasma, Xfce and LXDE, and from special disc 1 CDs.[109][110]默认桌面可以从 GNOME、KDE Plasma、Xfce 和 LXDE 中的 DVD 启动菜单中选择，也可以从专用光盘 1 CD 中选择。[109][110]
Debian releases live install images for CDs, DVDs and USB thumb drives, for IA-32 and x86-64 architectures, and with a choice of desktop environments. These Debian Live images allow users to boot from removable media and run Debian without affecting the contents of their computer. A full install of Debian to the computer's hard drive can be initiated from the live image environment.[111] Personalized images can be built with the live-build tool for discs, USB drives and for network booting purposes.[112] Installation images are hybrid on some architectures and can be used to create a bootable USB drive (Live USB).[113]Debian 发布适用于 IA-32 和 x86-64 架构的 CD、DVD 和 USB 拇指驱动器的实时安装映像，并可选择桌面环境。这些 Debian Live 映像允许用户从可移动媒体启动并运行 Debian，而不会影响他们计算机的内容。可以从实时映像环境启动 Debian 到计算机硬盘驱动器的完整安装。 [111]可以使用实时构建工具构建个性化图像，用于光盘、USB 驱动器和网络启动目的。[112]安装映像在某些架构上是混合的，可用于创建可启动 USB 驱动器（Live USB）。[113]
Package management operations can be performed with different tools available on Debian, from the lowest level command dpkg to graphical front-ends like Synaptic. The recommended standard for administering packages on a Debian system is the apt toolset.[114]包管理操作可以使用 Debian 上可用的不同工具来执行，从最低级别的命令 dpkg 到像 Synaptic 这样的图形前端。在 Debian 系统上管理软件包的推荐标准是 apt 工具集。 [114]
dpkg provides the low-level infrastructure for package management.[115] The dpkg database contains the list of installed software on the current system. The dpkg command tool does not know about repositories. The command can work with local .deb package files, and information from the dpkg database.[116]dpkg 为包管理提供低级基础设施。 [115] dpkg 数据库包含当前系统上已安装软件的列表。 dpkg 命令工具不知道存储库。该命令可以处理本地 .deb 包文件，以及来自 dpkg 数据库的信息。[116]
Using Aptitude to view Debian package details使用 Aptitude 查看 Debian 软件包详细信息
Package installed with Aptitude随 Aptitude 安装的软件包
An Advanced Packaging Tool (APT) allows administering an installed Debian system to retrieve and resolve package dependencies from repositories. APT tools share dependency information and cached packages.[114]Advanced Packaging Tool (APT) 允许管理已安装的 Debian 系统以从存储库中检索和解析软件包依赖性。 APT 工具共享依赖信息和缓存包。 [114]
The apt command itself is intended as an end user interface and enables some options better suited for interactive usage by default compared to more specialized APT like apt-get and apt-cache explained below.apt 命令本身旨在作为最终用户界面，并且与更专业的 APT（如下面解释的 apt-get 和 apt-cache）相比，默认情况下启用一些更适合交互式使用的选项。
apt-get and apt-cache are command tools of the standard apt package. apt-get installs and removes packages, and apt-cache is used for searching packages and displaying package information.[114]apt-get 和 apt-cache 是标准 apt 包的命令工具。 apt-get 安装和删除包，apt-cache 用于搜索包和显示包信息。[114]
Screenshot of GDebi Package installerGDebi 包安装程序的屏幕截图
GDebi is an APT tool which can be used in command-line and on the GUI.[117] GDebi can install a local .deb file via the command line like the dpkg command, but with access to repositories to resolve dependencies.[118] Other graphical front-ends for APT include Software Center,[119]Synaptic[120] and Apper.[121]GDebi 是一个 APT 工具，可以在命令行和 GUI 上使用。 [117] GDebi 可以像 dpkg 命令一样通过命令行安装本地 .deb 文件，但可以访问存储库来解决依赖关系。 [118] APT 的其他图形前端包括软件中心、[119] Synaptic[120] 和 Apper。[121]
GNOME Software is a graphical front-end for PackageKit, which itself can work on top of various software packaging systems.
GNOME Software 是 PackageKit 的图形前端，它本身可以在各种软件打包系统之上工作。
The Debian Free Software Guidelines (DFSG) define the distinctive meaning of the word "free" as in "free and open-source software".[122] Packages that comply with these guidelines, usually under the GNU General Public License, Modified BSD License or Artistic License,[123] are included inside the main area;[124] otherwise, they are included inside the non-free and contrib areas. These last two areas are not distributed within the official installation media, but they can be adopted manually.[122]Debian 自由软件指南 (DFSG) 定义了“自由”一词在“自由和开源软件”中的独特含义。 [122]符合这些指南的软件包，通常在 GNU 通用公共许可证、修改后的 BSD 许可证或艺术许可证下，[123] 包含在主要区域中；[124] 否则，它们包含在非自由和贡献区域中。最后两个区域没有在官方安装介质中分发，但可以手动采用。 [122]
Non-free includes packages that do not comply with the DFSG,[125] such as documentation with invariant sections and proprietary software,[126][127] and legally questionable packages.[125] Contrib includes packages which do comply with the DFSG but fail other requirements. For example, they may depend on packages which are in non-free or requires such for building them.[125]非免费包括不符合 DFSG 的软件包，[125] 例如具有不变部分和专有软件的文档，[126][127] 和法律上有问题的软件包。[125] Contrib 包含确实符合 DFSG 但未满足其他要求的软件包。例如，它们可能依赖于非自由的包或需要这样的包来构建它们。 [125]
Richard Stallman and the Free Software Foundation have criticized the Debian project for hosting the non-free repository and because the contrib and non-free areas are easily accessible,[128][129] an opinion echoed by some in Debian including the former project leader Wichert Akkerman.[130] The internal dissent in the Debian project regarding the non-free section has persisted,[131] but the last time it came to a vote in 2004, the majority decided to keep it.[132]Richard Stallman 和自由软件基金会批评 Debian 项目托管非自由存储库，因为 contrib 和非自由区域很容易访问，[128][129] Debian 中的一些人（包括前项目负责人）也赞同这一观点维切特·阿克曼 [130] Debian 项目中关于非自由部分的内部异议一直存在，[131] 但上一次投票是在 2004 年，大多数人决定保留它。 [132]
The most popular optional Linux cross-distribution package manager are graphical (front-ends) package managers. They are available within the official Debian Repository but are not installed by default. They are widely popular with both Debian users and Debian software developers who are interested in installing the most recent versions of application or using the cross-distribution package manager built-in sandbox environment. While at the same time remaining in control of the security.[133][134]最流行的可选 Linux 交叉分发包管理器是图形（前端）包管理器。它们在官方 Debian 存储库中可用，但默认情况下不安装。它们广受 Debian 用户和 Debian 软件开发人员的欢迎，他们对安装最新版本的应用程序或使用跨发行版包管理器内置沙箱环境感兴趣。同时保持对安全的控制。[133][134]
Four most popular cross-distribution package managers, sorted in alphabetical order:四个最流行的跨发行版包管理器，按字母顺序排序：
AppImage Linux distribution-agnostic binary software deploymentAppImage Linux 发行版不可知的二进制软件部署
Flatpak software code is owned and maintained by the not for profit Flatpak Team, with an open source LGPL-2.1-only license.Flatpak 软件代码由非营利性 Flatpak 团队拥有和维护，具有开源 LGPL-2.1-only 许可证。
Homebrew software code is owned and maintained by its original author Max Howell, with an open source BSD 2-Clause License.Homebrew 软件代码由其原始作者 Max Howell 拥有和维护，并具有开源 BSD 2-Clause 许可证。
A Debian 10.0 Buster box coverDebian 10.0 Buster 盒盖
Three branches of Debian (also called releases, distributions or suites) are regularly maintained:[135]Debian 的三个分支（也称为发行版、发行版或套件）定期维护：[135]
Stable is the current release and targets stable and well-tested software needs.[136]Stable is made by freezing Testing for a few months where bugs are fixed and packages with too many bugs are removed; then the resulting system is released as stable. It is updated only if major security or usability fixes are incorporated.[124] This branch has an optional backports service that provides more recent versions of some software.[63]Stable's CDs and DVDs can be found in the Debian website.[106]Stable 是当前版本，目标是稳定和经过良好测试的软件需求。 [136]稳定是通过冻结几个月的测试来实现的，其中修复了错误并删除了有太多错误的包；然后将生成的系统发布为稳定版。只有在合并了主要的安全或可用性修复程序时才会更新。 [124]这个分支有一个可选的向后移植服务，提供一些软件的更新版本。 [63] Stable 的 CD 和 DVD 可以在 Debian 网站上找到。[106]
Testing is the preview branch that will eventually become the next major release. The packages included in this branch have had some testing in unstable but they may not be fit for release yet. It contains newer packages than stable but older than unstable. This branch is updated continually until it is frozen.[124]Testing's CDs and DVDs can be found on the Debian website.[106]测试是最终将成为下一个主要版本的预览分支。这个分支中包含的包已经在不稳定中进行了一些测试，但它们可能还不适合发布。它包含比 stable 更新但比 unstable 旧的包。这个分支不断更新，直到它被冻结。 [124]测试的 CD 和 DVD 可以在 Debian 网站上找到。[106]
Unstable, always codenamed sid, is the trunk. Packages are accepted without checking the distribution as a whole.[124] This branch is usually run by software developers who participate in a project and need the latest libraries available, and by those who prefer bleeding-edge software.[135] Debian does not provide full Sid installation discs, but rather a minimal ISO that can be used to install over a network connection. Additionally, this branch can be installed through a system upgrade from stable or testing.[137]不稳定，始终代号为 sid，是主干。包裹被接受而不检查整个分布。[124]该分支通常由参与项目并需要最新可用库的软件开发人员以及喜欢前沿软件的人员运行。 [135] Debian 不提供完整的 Sid 安装光盘，而是提供可用于通过网络连接进行安装的最小 ISO。此外，可以通过从稳定版或测试版升级系统来安装此分支。 [137]
Other branches in Debian:
Debian 中的其他分支：
Oldstable is the prior stable release.[124] It is supported by the Debian Security Team until one year after a new stable is released, and since the release of Debian 6, for another 2 years through the Long Term Support project.[138] Eventually, oldstable is moved to a repository for archived releases.[124] Debian 10 is the current Oldstable release.Oldstable 是之前的稳定版本。 [124]它由 Debian 安全团队提供支持，直到新稳定版发布后一年，以及自 Debian 6 发布后，通过长期支持项目再支持 2 年。 [138]最终，oldstable 被移动到一个存储库中以用于存档版本。[124] Debian 10 是当前的 Oldstable 版本。
Oldoldstable is the prior oldstable release. It is supported by the Long Term Support community. Eventually, oldoldstable is moved to a repository for archived releases. Debian 9 is the current Oldoldstable release.Oldoldstable 是之前的 oldstable 版本。它由长期支持社区提供支持。最终，oldoldstable 被移动到一个存储库中以用于存档版本。 Debian 9 是当前的 Oldoldstable 版本。
Experimental is a temporary staging area of highly experimental software that is likely to break the system. It is not a full distribution and missing dependencies are commonly found in unstable, where new software without the damage chance is normally uploaded.[124]Experimental 是高度实验性软件的临时暂存区，可能会破坏系统。它不是一个完整的发行版，并且在不稳定的情况下通常会发现缺少依赖项，通常会上传没有损坏机会的新软件。 [124]
The snapshot archive provides older versions of the branches. They may be used to install a specific older version of some software.[139]快照存档提供旧版本的分支。它们可用于安装某些软件的特定旧版本。 [139]
Stable and oldstable get minor updates, called point releases; as of August 2021, the stable release is version 11.0,[140] released on August 14, 2021; 19 months ago (), and the oldstable release is version 10.10.[141]Stable 和 oldstable 获得小更新，称为点发布；截至 2021 年 8 月，稳定版本为 11.0，[140] 于 2021 年 8 月 14 日发布； 19 个月前，旧稳定版是 10.10 版。[141]
The numbering scheme for the point releases up to Debian 4.0 was to include the letter r (for revision)[142] after the main version number and then the number of the point release; for example, the latest point release of version 4.0 is 4.0r9.[143] This scheme was chosen because a new dotted version would make the old one look obsolete and vendors would have trouble selling their CDs.[144]Debian 4.0 之前的单点发行编号方案是在主版本号之后包含字母 r（用于修订）[142]，然后是单点发行的编号；例如，4.0 版的最新版本是 4.0r9.[143]之所以选择这个方案，是因为新的带点的版本会使旧版本看起来过时，而且供应商在销售他们的 CD 时会遇到麻烦。 [144]
From Debian 5.0, the numbering scheme of point releases was changed, conforming to the GNU version numbering standard;[145] the first point release of Debian 5.0 was 5.0.1 instead of 5.0r1.[146] The numbering scheme was once again changed for the first Debian 7 update, which was version 7.1.[147] The r scheme is no longer in use, but point release announcements include a note about not throwing away old CDs.[148]从 Debian 5.0 开始，点发布的编号方案发生了变化，符合 GNU 版本编号标准；[145] Debian 5.0 的第一个点发布是 5.0.1 而不是 5.0r1。[146]第一次 Debian 7 更新的编号方案再次发生变化，即版本 7.1。[147] r 方案不再使用，但点发布公告包括关于不要扔掉旧 CD 的说明。 [148]
Debian is one of the most popular Linux distributions, and many other distributions have been created from the Debian codebase.[149] As of 2021, DistroWatch lists 121 active Debian derivatives.[150] The Debian project provides its derivatives with guidelines for best practices and encourages derivatives to merge their work back into Debian.[151][152]Debian 是最流行的 Linux 发行版之一，许多其他发行版都是从 Debian 代码库创建的。 [149]截至 2021 年，DistroWatch 列出了 121 个活跃的 Debian 衍生产品。[150] Debian 项目为其衍生产品提供最佳实践指南，并鼓励衍生产品将他们的工作合并回 Debian。[151][152]
Debian Pure Blends are subsets of a Debian release configured out-of-the-box for users with particular skills and interests.[153] For example, Debian Jr. is made for children, while Debian Science is for researchers and scientists.[154] The complete Debian distribution includes all available Debian Pure Blends.[153] "Debian Blend" (without "Pure") is a term for a Debian-based distribution that strives to become part of mainstream Debian, and have its extra features included in future releases.[155]Debian Pure Blends 是为具有特殊技能和兴趣的用户配置的开箱即用的 Debian 发行版的子集。 [153]例如，Debian Jr. 是为儿童设计的，而 Debian Science 是为研究人员和科学家设计的。 [154]完整的 Debian 发行版包括所有可用的 Debian Pure Blends。[153] “Debian Blend”（没有“Pure”）是一个基于 Debian 的发行版的术语，它努力成为主流 Debian 的一部分，并在未来的版本中包含其额外功能。 [155]
Logo of Debian GNU/kFreeBSDDebian GNU/kFreeBSD 标志
Debian GNU/kFreeBSD is a discontinued[156] Debian flavor. It used the FreeBSDkernel and GNUuserland. The majority of software in Debian GNU/kFreeBSD was built from the same sources as Debian, with some kernel packages from FreeBSD. The k in kFreeBSD is an abbreviation for kernel, which refers to the FreeBSD kernel. Before discontinuing the project, Debian maintained i386 and amd64 ports. The last version of Debian kFreeBSD was Debian 8 (Jessie) RC3. Debian GNU/kFreeBSD was created in 2002.[157] It was included in Debian 6.0 (Squeeze) as a technology preview, and in Debian 7.0 (Wheezy) as an official port. Debian GNU/kFreeBSD was discontinued as an officially supported platform as of Debian 8.0. Debian developers cited OSS, pf, jails, NDIS, and ZFS as reasons for being interested in the FreeBSD kernel.[158] It has not been updated since Debian 8.[159] As of July 2019, however, the operating system continues to be maintained unofficially.[160]Debian GNU/kFreeBSD 已停产[156] Debian 风格。它使用 FreeBSD 内核和 GNU 用户空间。 Debian GNU/kFreeBSD 中的大部分软件都是从与 Debian 相同的来源构建的，一些内核包来自 FreeBSD。 kFreeBSD中的k是kernel的缩写，指的是FreeBSD内核。在终止该项目之前，Debian 维护了 i386 和 amd64 端口。 Debian kFreeBSD 的最新版本是 Debian 8 (Jessie) RC3。 Debian GNU/kFreeBSD 创建于 2002 年。[157]它作为技术预览包含在 Debian 6.0 (Squeeze) 中，并作为官方端口包含在 Debian 7.0 (Wheezy) 中。从 Debian 8.0 开始，Debian GNU/kFreeBSD 不再作为官方支持的平台。 Debian 开发人员将 OSS、pf、jails、NDIS 和 ZFS 列为对 FreeBSD 内核感兴趣的原因。 [158]自 Debian 8 以来就没有更新过。[159]然而，截至 2019 年 7 月，该操作系统仍在继续进行非正式维护。 [160]
Logo of GNU HurdGNU 赫德的标志
Debian GNU/Hurd running on Xfce在 Xfce 上运行的 Debian GNU/Hurd
Debian GNU/Hurd is a flavor based on the Hurdmicrokernel, instead of Linux. Debian GNU/Hurd has been in development since 1998,[161] and made a formal release in May 2013, with 78% of the software packaged for Debian GNU/Linux ported to the GNU Hurd.[162] Hurd is not yet an official Debian release, and is maintained and developed as an unofficial port. Debian GNU/Hurd is distributed as an installer CD (running the official Debian installer) or ready-to-run virtual disk image (Live CD, Live USB). The CD uses the IA-32 architecture, making it compatible with IA-32 and x86-64 PCs. The current version of Debian GNU/Hurd is 2021, published in August 2021.[163]Debian GNU/Hurd 是基于 Hurd 微内核的一种风格，而不是 Linux。 Debian GNU/Hurd 自 1998 年以来一直在开发，[161] 并于 2013 年 5 月正式发布，78% 的 Debian GNU/Linux 打包软件移植到 GNU Hurd。 [162] Hurd 还不是正式的 Debian 发行版，并且作为非官方端口进行维护和开发。 Debian GNU/Hurd 作为安装程序 CD（运行官方 Debian 安装程序）或准备运行的虚拟磁盘映像（Live CD、Live USB）分发。 CD 使用 IA-32 架构，使其与 IA-32 和 x86-64 PC 兼容。 Debian GNU/Hurd 的当前版本是 2021，发布于 2021 年 8 月。[163]
Mobian is a Debian derivative designed for mobile devices. It supports a number of devices including the Librem 5, PinePhone and OnePlus 6[164]Mobian 是为移动设备设计的 Debian 衍生产品。它支持多种设备，包括 Librem 5、PinePhone 和 OnePlus 6[164]
The "swirl" logo is said to represent magic smoke.“漩涡”标志据说代表魔法烟雾。
The Debian "swirl" logo was designed by Raul Silva[165][166] in 1999 as part of a contest to replace the semi-official logo that had been used.[167] The winner of the contest received an @Debian.org email address, and a set of Debian 2.1 install CDs for the architecture of their choice. Initially, the swirl was magic smoke arising from an also included bottle of an Arabian-style genie presented in black profile, but shortly after was reduced to the red smoke swirl for situations where space or multiple colours were not an option, and before long the bottle version effectively was superseded. There has been no official statement from the Debian project on the logo's meaning, but at the time of the logo's selection, it was suggested that the logo represented the magic smoke ( or the genie ) that made computers work.[168][169][170]Debian“漩涡”标志由 Raul Silva[165][166] 于 1999 年设计，作为替换已使用的半官方标志的竞赛的一部分。 [167]比赛的获胜者将收到一个@Debian.org 电子邮件地址，以及一套适用于他们选择的体系结构的 Debian 2.1 安装 CD。最初，漩涡是从一瓶阿拉伯风格的精灵中产生的魔法烟雾，但不久之后，在无法选择空间或多种颜色的情况下，它变成了红色的烟雾漩涡，不久之后瓶子版本有效地被取代了。 Debian 项目没有关于徽标含义的官方声明，但在选择徽标时，有人建议该徽标代表使计算机工作的魔法烟雾（或精灵）。[168][169] [170]
One theory about the origin of the Debian logo is that Buzz Lightyear, the chosen character for the first named Debian release, has a swirl in his chin.[171][172]Stefano Zacchiroli also suggested that this swirl is the Debian one.[173] Buzz Lightyear's swirl is a more likely candidate as the codenames for Debian are names of Toy Story characters. The former Debian project leader Bruce Perens used to work for Pixar and is credited as a studio tools engineer on Toy Story 2 (1999).
关于 Debian 徽标起源的一种理论是巴斯光年，第一个命名的 Debian 版本的选定角色，下巴上有一个漩涡。 [171][172] Stefano Zacchiroli 还建议这个漩涡是 Debian 的。 [173]巴斯光年的漩涡更有可能成为候选者，因为 Debian 的代号是玩具总动员角色的名字。前 Debian 项目负责人 Bruce Perens 曾在 Pixar 工作，并被誉为玩具总动员 2 (Toy Story 2) (1999) 的工作室工具工程师。
Hardware requirements are at least those of the kernel and the GNU toolsets.[174] Debian's recommended system requirements depend on the level of installation, which corresponds to increased numbers of installed components:[175]硬件要求至少是内核和 GNU 工具集的要求。 [174] Debian 推荐的系统要求取决于安装级别，这对应于安装组件数量的增加：[175]
The real minimum memory requirements depend on the architecture and may be much less than the numbers listed in this table. It is possible to install Debian with 170 MB of RAM for x86-64;[175] the installer will run in low memory mode and it is recommended to create a swap partition.[109] The installer for z/Architecture requires about 20 MB of RAM, but relies on network hardware.[175][176] Similarly, disk space requirements, which depend on the packages to be installed, can be reduced by manually selecting the packages needed.[175] As of May 2019, no Pure Blend exists that would lower the hardware requirements easily.[177]实际的最低内存要求取决于体系结构，可能远小于此表中列出的数字。可以为 x86-64 安装具有 170 MB RAM 的 Debian；[175] 安装程序将在低内存模式下运行，建议创建一个交换分区。[109] z/Architecture 的安装程序需要大约 20 MB 的 RAM，但依赖于网络硬件。[175][176]同样，磁盘空间需求取决于要安装的包，可以通过手动选择所需的包来减少。 [175]截至 2019 年 5 月，不存在可以轻松降低硬件要求的 Pure Blend。 [177]
It is possible to run graphical user interfaces on older or low-end systems, but the installation of window managers instead of desktop environments is recommended, as desktop environments are more resource intensive. Requirements for individual software vary widely and must be considered, with those of the base operating environment.[175]可以在较旧或低端系统上运行图形用户界面，但建议安装窗口管理器而不是桌面环境，因为桌面环境需要更多资源。对个别软件的要求与基本操作环境的要求差别很大，必须加以考虑。 [175]
armel: Little-endianARM architecture (ARMv4T instruction set)[180] on various embedded systems (embedded application binary interface (EABI)), although support has ended after Busterarmel：各种嵌入式系统（嵌入式应用程序二进制接口（EABI））上的小端 ARM 架构（ARMv4T 指令集）[180]，尽管在 Buster 之后支持已经结束
armhf: ARM hard-float architecture (ARMv7 instruction set) requiring hardware with a floating-point unitarmhf：ARM 硬浮点架构（ARMv7 指令集）要求硬件带有浮点单元
i386: IA-32 architecture with 32-bit userland, compatible with x86-64 machines[174]i386：具有 32 位用户域的 IA-32 架构，与 x86-64 机器兼容[174]
kfreebsd-amd64: Kernel of FreeBSD on x86-64 architecturekfreebsd-amd64：x86-64 架构上的 FreeBSD 内核
kfreebsd-i386: Kernel of FreeBSD on IA-32 architecturekfreebsd-i386：基于 IA-32 架构的 FreeBSD 内核
m68k: Motorola 68k architecture on Amiga, Atari, Macintosh and various embedded VME systemsm68k：在 Amiga、Atari、Macintosh 和各种嵌入式 VME 系统上的 Motorola 68k 架构
powerpc: 32-bit PowerPCpowerpc：32 位 PowerPC
ppc64: PowerPC64 architecture supporting 64-bit PowerPC CPUs with VMXppc64：PowerPC64 架构，支持带 VMX 的 64 位 PowerPC CPU
riscv64: 64-bit RISC-V this RISC-V - Debian Wiki official Debian page collect many useful info, links and report for tested hardwareriscv64: 64-bit RISC-V 这个 RISC-V - Debian Wiki 官方 Debian 页面收集了许多有用的信息、链接和测试硬件的报告
sparc64: Sun SPARC architecture with 64-bit userlandsparc64：具有 64 位用户空间的 Sun SPARC 体系结构
x32: x32 ABI userland for x86-64[182]x32：x86-64 的 x32 ABI 用户空间 [182]
Debian supports a variety of ARM-based NAS devices. The NSLU2 was supported by the installer in Debian 4.0 and 5.0,[183] and Martin Michlmayr is providing installation tarballs since version 6.0.[184] Other supported NAS devices are the Buffalo Kurobox Pro,[185] GLAN Tank, Thecus N2100[186] and QNAP Turbo Stations.[185]Debian 支持各种基于 ARM 的 NAS 设备。 Debian 4.0 和 5.0 中的安装程序支持 NSLU2，[183] 并且 Martin Michlmayr 从 6.0.[184] 版本开始提供安装压缩包其他支持的 NAS 设备包括 Buffalo Kurobox Pro、[185] GLAN Tank、Thecus N2100[186] 和 QNAP Turbo Stations。[185]
Devices based on the Kirkwood system on a chip (SoC) are supported too, such as the SheevaPlug plug computer and OpenRD products.[187] There are efforts to run Debian on mobile devices, but this is not a project goal yet since the Debian Linux kernel maintainers would not apply the needed patches.[188] Nevertheless, there are packages for resource-limited systems.[189]也支持基于 Kirkwood 片上系统 (SoC) 的设备，例如 SheevaPlug 插头计算机和 OpenRD 产品。 [187]人们努力在移动设备上运行 Debian，但这还不是项目目标，因为 Debian Linux 内核维护者不会应用所需的补丁。 [188]尽管如此，还是有针对资源有限系统的软件包。 [189]
There are efforts to support Debian on wireless access points.[190] Debian is known to run on set-top boxes.[191] Work is ongoing to support the AM335x processor,[192] which is used in electronic point of service solutions.[193] Debian may be customized to run on cash machines.[194]有一些努力在无线接入点上支持 Debian。 [190] Debian 以在机顶盒上运行而闻名。 [191]支持 AM335x 处理器的工作正在进行中，[192] 它用于电子服务点解决方案。 [193] Debian 可以定制为在提款机上运行。 [194]
BeagleBoard, a low-power open-source hardware single-board computer (made by Texas Instruments) has switched to Debian Linux preloaded on its Beaglebone Black board's flash.
BeagleBoard 是一种低功耗开源硬件单板计算机（由 Texas Instruments 制造），已切换到预装在其 Beaglebone Black 板闪存上的 Debian Linux。
Roqos Core, manufactured by Roqos, is a x86-64 based IPS firewall router running Debian Linux.
Roqos Core 由 Roqos 制造，是一款基于 x86-64 的 IPS 防火墙路由器，运行 Debian Linux。
Debian's policies and team efforts focus on collaborative software development and testing processes.[6] As a result, a new major release tends to occur every two years with revision releases that fix security issues and important problems.[142][61] The Debian project is a volunteer organization with three foundational documents:
Debian 的政策和团队努力专注于协作软件开发和测试过程。 [6]因此，新的主要版本往往每两年发布一次，其中包含修复安全问题和重要问题的修订版。[142][61] Debian 项目是一个志愿者组织，拥有三个基本文件：
The Debian Social Contract defines a set of basic principles by which the project and its developers conduct affairs.[122]Debian Social Contract 定义了项目及其开发人员处理事务所依据的一组基本原则。 [122]
The Debian Free Software Guidelines define the criteria for "free software" and thus what software is permissible in the distribution. These guidelines have been adopted as the basis of the Open Source Definition. Although this document can be considered separate, it formally is part of the Social Contract.[122]Debian Free Software Guidelines 定义了“自由软件”的标准以及发行版中允许使用的软件。这些准则已被采纳为开源定义的基础。尽管这份文件可以被认为是独立的，但它在形式上是社会契约的一部分。 [122]
The Debian Constitution describes the organizational structure for formal decision-making within the project, and enumerates the powers and responsibilities of the Project Leader, the Secretary and other roles.[29]Debian 章程描述了项目内正式决策的组织结构，并列举了项目负责人、秘书和其他角色的权力和责任。 [29]
Debian developers are organized in a web of trust.[195] There are at present about one thousand active Debian developers,[196][197] but it is possible to contribute to the project without being an official developer.[198]Debian 开发人员组织在一个信任的网络中。 [195]目前大约有 1000 名活跃的 Debian 开发人员，[196][197] 但即使不是官方开发人员也可以为该项目做出贡献。 [198]
The project maintains official mailing lists and conferences for communication and coordination between developers.[124][199] For issues with single packages and other tasks,[200] a public bug tracking system is used by developers and end users. Internet Relay Chat is also used for communication among developers[124] and to provide real time help.[201]该项目维护官方邮件列表和会议，用于开发人员之间的沟通和协调。[124][199]对于单个包和其他任务的问题，[200] 开发人员和最终用户使用公共错误跟踪系统。 Internet 中继聊天还用于开发人员之间的交流[124] 和提供实时帮助。[201]
Debian is supported by donations made to organizations authorized by the leader.[29] The largest supporter is Software in the Public Interest, the owner of the Debian trademark, manager of the monetary donations[202] and umbrella organization for various other community free software projects.[203]Debian 得到领导授权的组织的捐款支持。 [29]最大的支持者是 Software in the Public Interest，它是 Debian 商标的所有者、金钱捐赠的管理者[202] 以及各种其他社区自由软件项目的伞状组织。 [203]
A Project Leader is elected once per year by the developers. The leader has special powers, but they are not absolute, and appoints delegates to perform specialized tasks. Delegates make decisions as they think is best, taking into account technical criteria and consensus. By way of a General Resolution, the developers may recall the leader, reverse a decision made by the leader or a delegate, amend foundational documents and make other binding decisions.[29] The voting method is based on the Schulze method (Cloneproof Schwartz Sequential Dropping).[30]项目负责人每年由开发商选出一次。领导者有特殊的权力，但不是绝对的，并任命代表执行专门的任务。代表们根据他们认为最好的方式做出决定，同时考虑技术标准和共识。通过一般决议，开发人员可以召回领导者，推翻领导者或代表做出的决定，修改基础文件并做出其他具有约束力的决定。 [29]投票方法基于 Schulze 方法（Cloneproof Schwartz Sequential Dropping）[30]。
Project leadership is distributed occasionally. Branden Robinson was helped by the Project Scud, a team of developers that assisted the leader,[205] but there were concerns that such leadership would split Debian into two developer classes.[206] Anthony Towns created a supplemental position, Second In Charge (2IC), that shared some powers of the leader.[207] Steve McIntyre was 2IC and had a 2IC himself.[208]项目领导权是偶尔分配的。 Branden Robinson 得到了 Project Scud 的帮助，这是一个协助领导者的开发团队，[205] 但有人担心这样的领导会把 Debian 分成两个开发者类别。 [206]安东尼·唐斯 (Anthony Towns) 设立了一个补充职位，即第二负责人 (2IC)，该职位分享了领导者的一些权力。 [207] Steve McIntyre 是 2IC，他自己也有 2IC。[208]
One important role in Debian's leadership is that of a release manager.[209] The release team sets goals for the next release, supervises the processes and decides when to release. The team is led by the next release managers and stable release managers.[210] Release assistants were introduced in 2003.[211]Debian 领导力中的一个重要角色是发布管理员。 [209]发布团队为下一次发布设定目标，监督流程并决定何时发布。该团队由下一个发布经理和稳定发布经理领导。 [210]发布助手于 2003 年推出。 [211]
The Debian Project has an influx of applicants wishing to become developers.[212] These applicants must undergo a vetting process which establishes their identity, motivation, understanding of the project's principles, and technical competence.[213] This process has become much harder throughout the years.[214]Debian 项目有大量希望成为开发人员的申请者。 [212]这些申请人必须经过审查程序，以确定他们的身份、动机、对项目原则的理解和技术能力。 [213]这些年来，这个过程变得更加困难。 [214]
Debian developers join the project for many reasons. Some that have been cited include:
Debian 开发人员加入该项目的原因有很多。一些被引用的包括：
Debian is their main operating system and they want to promote Debian[215]Debian 是他们的主要操作系统，他们想推广 Debian[215]
To improve the support for their favorite technology[216]改进对他们最喜欢的技术的支持[216]
They are involved with a Debian derivative[217]他们参与了 Debian 衍生产品[217]
To make their Debian maintenance work easier[219]使他们的 Debian 维护工作更容易 [219]
Debian developers may resign their positions at any time or, when deemed necessary, they can be expelled.[29] Those who follow the retiring protocol are granted the "emeritus" status and they may regain their membership through a shortened new member process.[220]Debian 开发人员可以随时辞职，或者在认为有必要时，可以开除他们。 [29]那些遵循退休协议的人被授予“退休”身份，他们可以通过缩短的新成员程序重新获得成员资格。 [220]
Flowchart of the life cycle of a Debian packageDebian 软件包生命周期流程图
Each software package has a maintainer that may be either one person or a team of Debian developers and non-developer maintainers.[221][222] The maintainer keeps track of upstream releases, and ensures that the package coheres with the rest of the distribution and meets the standards of quality of Debian. Packages may include modifications introduced by Debian to achieve compliance with Debian Policy, even to fix non-Debian specific bugs, although coordination with upstream developers is advised.[220]每个软件包都有一个维护者，可以是一个人，也可以是一组 Debian 开发人员和非开发人员维护人员。[221][222]维护者跟踪上游版本，并确保软件包与发行版的其余部分保持一致并符合 Debian 的质量标准。软件包可能包含由 Debian 引入的修改以符合 Debian 政策，甚至修复非 Debian 特定的错误，尽管建议与上游开发人员协调。 [220]
The maintainer releases a new version by uploading the package to the "incoming" system, which verifies the integrity of the packages and their digital signatures. If the package is found to be valid, it is installed in the package archive into an area called the "pool" and distributed every day to hundreds of mirrors worldwide. The upload must be signed using OpenPGP-compatible software.[124] All Debian developers have individual cryptographic key pairs.[223] Developers are responsible for any package they upload even if the packaging was prepared by another contributor.[224]维护者通过将包上传到“传入”系统来发布新版本，该系统验证包及其数字签名的完整性。如果发现包有效，它会在包存档中安装到一个称为“池”的区域，并每天分发到全球数百个镜像。上传必须使用兼容 OpenPGP 的软件进行签名。 [124]所有 Debian 开发人员都有单独的加密密钥对。 [223]开发人员应对他们上传的任何包负责，即使该包是由其他贡献者准备的。 [224]
Initially, an accepted package is only available in the unstable branch.[124] For a package to become a candidate for the next release, it must migrate to the Testing branch by meeting the following:[225]最初，接受的包仅在不稳定分支中可用。 [124]要成为下一个版本的候选包，它必须通过满足以下条件迁移到测试分支：[225]
It has been in unstable for a certain length of time that depends on the urgency of the changes.它在一段时间内处于不稳定状态，具体时间长短取决于更改的紧迫性。
It does not have "release-critical" bugs, except for the ones already present in Testing. Release-critical bugs are those considered serious enough that they make the package unsuitable for release.除了测试中已经存在的错误外，它没有“发布关键”错误。发布关键错误是那些被认为足够严重以至于它们使包不适合发布的错误。
There are no outdated versions in unstable for any release ports.对于任何发布端口，unstable 中都没有过时的版本。
The migration does not break any packages in Testing.迁移不会破坏测试中的任何包。
Its dependencies can be satisfied by packages already in Testing or by packages being migrated at the same time.它的依赖关系可以由已经在测试中的包或同时迁移的包来满足。
The migration is not blocked by a freeze.迁移不会被冻结阻止。
Thus, a release-critical bug in a new version of a shared library on which many packages depend may prevent those packages from entering Testing, because the updated library must meet the requirements too.[226] From the branch viewpoint, the migration process happens twice per day, rendering Testing in perpetual beta.[124]因此，许多包所依赖的共享库的新版本中的发布关键错误可能会阻止这些包进入测试，因为更新后的库也必须满足要求。 [226]从分支的角度来看，迁移过程每天发生两次，呈现永久测试版中的测试。 [124]
Periodically, the release team publishes guidelines to the developers in order to ready the release. A new release occurs after a freeze, when all important software is reasonably up-to-date in the Testing branch and any other significant issues are solved. At that time, all packages in the testing branch become the new stable branch.[124] Although freeze dates are time-based,[61] release dates are not, which are announced by the release managers a couple of weeks beforehand.[227]发布团队定期向开发人员发布指南，以便为发布做好准备。当所有重要软件在测试分支中都合理更新并且任何其他重要问题都得到解决时，冻结后会出现新版本。那时，测试分支中的所有包都成为新的稳定分支。[124]尽管冻结日期是基于时间的，[61] 发布日期不是，发布经理会提前几周宣布。 [227]
A version of a package can belong to more than one branch, usually testing and unstable. It is possible for a package to keep the same version between stable releases and be part of oldstable, stable, testing and unstable at the same time.[228] Each branch can be seen as a collection of pointers into the package "pool" mentioned above.[124]一个包的一个版本可以属于多个分支，通常是testing和unstable。一个包有可能在稳定版本之间保持相同的版本，并同时成为 oldstable、stable、testing 和 unstable 的一部分。 [228]每个分支都可以看作是指向上述包“池”的指针的集合。 [124]
One way to resolve the challenge of a release-critical bug in a new application version is the use of optional package managers. They allow software developers to use sandbox environments, while at the same time remaining in control of security.[133][134] Another benefit of a cross-distribution package manager is that they allow application developers to directly provide updates to users without going through distributions, and without having to package and test the application separately for each distribution.[229]解决新应用程序版本中发布关键错误挑战的一种方法是使用可选包管理器。它们允许软件开发人员使用沙箱环境，同时保持对安全性的控制。[133][134]跨发行版包管理器的另一个好处是，它们允许应用程序开发人员直接向用户提供更新，而无需通过发行版，也不必为每个发行版单独打包和测试应用程序。 [229]
A new stable branch of Debian gets released approximately every 2 years. It will receive official support for about 3 years with update for major security or usability fixes. Point releases will be available every several months as determined by Stable Release Managers (SRM).[230]Debian 的新稳定分支大约每 2 年发布一次。它将获得大约 3 年的官方支持，包括主要安全或可用性修复的更新。根据稳定版本管理器 (SRM) 的决定，点版本将每隔几个月发布一次。 [230]
Debian also launched its Long Term Support (LTS) project since Debian 6 (Debian Squeeze). For each Debian release, it will receive two years of extra security updates provided by LTS Team after its End Of Life (EOL). However, no point releases will be made. Now each Debian release can receive 5 years of security support in total.[231]自 Debian 6 (Debian Squeeze) 以来，Debian 还启动了长期支持 (LTS) 项目。对于每个 Debian 版本，它将在生命周期结束 (EOL) 后收到 LTS 团队提供的两年额外安全更新。但是，不会发布任何要点。现在每个 Debian 版本总共可以获得 5 年的安全支持。 [231]
The Debian project handles security through public disclosure. Debian security advisories are compatible with the Common Vulnerabilities and Exposures dictionary, are usually coordinated with other free software vendors and are published the same day a vulnerability is made public.[232][233] There used to be a security audit project that focused on packages in the stable release looking for security bugs;[234] Steve Kemp, who started the project, retired in 2011 but resumed his activities and applied to rejoin in 2014.[235][236]Debian 项目通过公开披露来处理安全问题。 Debian 安全建议与 Common Vulnerabilities and Exposures 词典兼容，通常与其他自由软件供应商协调，并在漏洞公开的同一天发布。[232][233]曾经有一个安全审计项目专注于稳定版本中的软件包以寻找安全漏洞；[234] 启动该项目的史蒂夫·肯普于 2011 年退休，但恢复活动并于 2014 年申请重新加入。[235][ [236]
The stable branch is supported by the Debian security team; oldstable is supported for one year.[138] Although Squeeze is not officially supported, Debian is coordinating an effort to provide long-term support (LTS) until February 2016, five years after the initial release, but only for the IA-32 and x86-64 platforms.[237]Testing is supported by the testing security team, but does not receive updates in as timely a manner as stable.[238]Unstable's security is left for the package maintainers.[138]稳定分支由 Debian 安全团队支持； oldstable 支持一年。[138]虽然 Squeeze 没有得到官方支持，但 Debian 正在努力提供长期支持 (LTS)，直到 2016 年 2 月，也就是首次发布后五年，但仅限于 IA-32 和 x86-64 平台。 [237]测试由测试安全团队支持，但不会像稳定那样及时地接收更新。 [238] Unstable 的安全性留给了软件包维护者。[138]
The Debian project offers documentation and tools to harden a Debian installation both manually and automatically.[239]AppArmor support is available and enabled by default since Buster.[240] Debian provides an optional hardening wrapper, and does not harden all of its software by default using gcc features such as PIE and buffer overflow protection, unlike operating systems such as OpenBSD,[241] but tries to build as many packages as possible with hardening flags.[242]Debian 项目提供文档和工具来手动和自动强化 Debian 安装。 [239]自 Buster 以来，AppArmor 支持可用并默认启用。[240] Debian 提供了一个可选的加固包装器，并且默认情况下不会使用 PIE 和缓冲区溢出保护等 gcc 功能加固其所有软件，这与 OpenBSD 等操作系统不同，[241] 但会尝试使用加固标志构建尽可能多的软件包.[242]
In May 2008, a Debian developer discovered that the OpenSSL package distributed with Debian and derivatives such as Ubuntu made a variety of security keys vulnerable to a random number generator attack, since only 32,767 different keys were generated.[243][244][245] The security weakness was caused by changes made in 2006 by another Debian developer in response to memory debugger warnings.[245][246] The complete resolution procedure was cumbersome because patching the security hole was not enough; it involved regenerating all affected keys and certificates.[247]2008 年 5 月，一名 Debian 开发人员发现，与 Debian 和 Ubuntu 等衍生产品一起分发的 OpenSSL 软件包使各种安全密钥容易受到随机数生成器攻击，因为只生成了 32,767 个不同的密钥。[243][244][245] ]安全漏洞是由另一位 Debian 开发人员在 2006 年为响应内存调试器警告所做的更改引起的。[245][246]完整的解决过程很麻烦，因为修补安全漏洞还不够；它涉及重新生成所有受影响的密钥和证书。 [247]
The cost of developing all of the packages included in Debian 5.0 Lenny (323 million lines of code) has been estimated to be about US$8 billion, using one method based on the COCOMO model.[248] As of 2016, Black Duck Open Hub estimates that the current codebase (74 million lines of code) would cost about US$1.4 billion to develop, using a different method based on the same model.[249][250]使用一种基于 COCOMO 模型的方法，开发 Debian 5.0 Lenny 中包含的所有软件包（3.23 亿行代码）的成本估计约为 80 亿美元。 [248]截至 2016 年，Black Duck Open Hub 估计当前代码库（7400 万行代码）的开发成本约为 14 亿美元，使用基于同一模型的不同方法。 [249][250]
A large number of forks and derivatives have been built upon Debian over the years. Among the more notable are Ubuntu, developed by Canonical Ltd. and first released in 2004, which has surpassed Debian in popularity with desktop users;[251]Knoppix, first released in the year 2000 and one of the first distributions optimized to boot from external storage; and Devuan, which gained attention in 2014 when it forked in disagreement over Debian's adoption of the systemd software suite, and has been mirroring Debian releases since 2017.[252][253]多年来，在 Debian 上构建了大量的分支和衍生产品。其中最著名的是由 Canonical Ltd. 开发并于 2004 年首次发布的 Ubuntu，它在桌面用户中的受欢迎程度已超过 Debian；[251] Knoppix，于 2000 年首次发布，是首批优化为从外部启动的发行版之一贮存;和 Devuan，它在 2014 年因对 Debian 采用 systemd 软件套件的分歧而引起关注，并且自 2017 年以来一直在镜像 Debian 版本。[252][253]
^"Publication de la mise à jour de Debian 11.6" (in French). December 17, 2022. Retrieved December 17, 2022.^ “Publication de la mise à jour de Debian 11.6”（法文）。 2022 年 12 月 17 日。2022 年 12 月 17 日检索。
^"Debian -- About". Debian. Debian. Archived from the original on January 17, 1999. Retrieved June 12, 2017.^ “Debian——关于”。德比安。德比安。原始存档于 1999 年 1 月 17 日。2017 年 6 月 12 日检索。
^ Jump up to: abc"ChangeLog". ibiblio. Archived from the original on January 6, 2017. Retrieved August 18, 2016.^ 跳转至： a b c "ChangeLog".书目。原始存档于 2017 年 1 月 6 日。2016 年 8 月 18 日检索。
^"Chapter 3 – Debian Releases". A Brief History of Debian. Debian Documentation Team. Archived from the original on August 17, 2011. Retrieved February 10, 2016.^ “第 3 章 – Debian 发布”。 Debian 简史。 Debian 文档团队。原始存档于 2011 年 8 月 17 日。2016 年 2 月 10 日检索。
^"Debian Releases - Codenames". Debian Wiki. Debian Wiki. Archived from the original on September 30, 2017. Retrieved July 25, 2017.^ “Debian 发行版 - 代号”。 Debian 维基百科。 Debian 维基百科。原始存档于 2017 年 9 月 30 日。2017 年 7 月 25 日检索。
^"Chapter 1 – Introduction – What is the Debian Project?". A Brief History of Debian. Debian. May 4, 2013. Archived from the original on December 22, 2015. Retrieved June 22, 2014.^ “第 1 章 – 简介 – 什么是 Debian 项目？”。 Debian 简史。德比安。 2013 年 5 月 4 日。原始存档于 2015 年 12 月 22 日。2014 年 6 月 22 日检索。
^Nixon, Robin (2010). Ubuntu: Up and Running. O'Reilly Media. p. 3. ISBN978-0-596-80484-8. Archived from the original on July 31, 2020. Retrieved June 22, 2014.^ 尼克松，罗宾 (2010)。 Ubuntu：启动并运行。奥莱利媒体。 p. 3. ISBN 978-0-596-80484-8。原始存档于 2020 年 7 月 31 日。2014 年 6 月 22 日检索。
^Hillesley, Richard (November 2, 2007). "Debian and the grass roots of Linux". IT Pro. Archived from the original on May 26, 2014. Retrieved May 25, 2014.^ Hillesley, Richard（2007 年 11 月 2 日）。 “Debian 和 Linux 的草根”。 IT 专家。原始存档于 2014 年 5 月 26 日。2014 年 5 月 25 日检索。
^ Jump up to: abcdScheetz, Dale (1998). The Debian Linux user's guide. Penngrove, Calif: Linux Press. ISBN0-9659575-1-9. OCLC42689229.^ 跳转至： a b c d Scheetz, Dale (1998)。 Debian Linux 用户指南。加利福尼亚州彭格罗夫：Linux 出版社。 ISBN 0-9659575-1-9。 OCLC 42689229。
^"Release-0.91". ibiblio. January 31, 1994. Archived from the original on September 24, 2015. Retrieved July 3, 2014.^ “发布 0.91”。书目。 1994 年 1 月 31 日。原始存档于 2015 年 9 月 24 日。2014 年 7 月 3 日检索。
^Murdock, Ian A. (January 6, 1994). "The Debian Linux Manifesto". ibiblio. Archived from the original on September 24, 2015. Retrieved July 17, 2014.^ Murdock, Ian A.（1994 年 1 月 6 日）。 “Debian Linux 宣言”。书目。原始存档于 2015 年 9 月 24 日。2014 年 7 月 17 日检索。
^ Jump up to: abcd"Chapter 3 – Debian Releases". A Brief History of Debian. Debian. May 4, 2013. Archived from the original on August 17, 2011. Retrieved June 22, 2014.^ 跳转至：a b c d “第 3 章 – Debian 发布”。 Debian 简史。德比安。 2013 年 5 月 4 日。原始存档于 2011 年 8 月 17 日。2014 年 6 月 22 日检索。
^ Jump up to: abcdef"Chapter 4 – A Detailed History". A Brief History of Debian. Debian. May 4, 2013. Archived from the original on December 21, 2019. Retrieved August 1, 2014.^ 跳转至：a b c d e f “第 4 章 – 详尽的历史”。 Debian 简史。德比安。 2013 年 5 月 4 日。原始存档于 2019 年 12 月 21 日。2014 年 8 月 1 日检索。
^Perens, Bruce (March 18, 1998). "I am leaving Debian". debian-user (Mailing list). Debian. Archived from the original on July 6, 2014. Retrieved June 5, 2014.^ Perens, Bruce（1998 年 3 月 18 日）。 “我要离开 Debian”。 debian-user（邮件列表）。德比安。原始存档于 2014 年 7 月 6 日。2014 年 6 月 5 日检索。
^Perens, Bruce (December 1, 1997). "Ian Jackson is the next Debian Project Leader". debian-announce (Mailing list). Debian. Archived from the original on September 9, 2015. Retrieved August 2, 2014.^ Perens, Bruce（1997 年 12 月 1 日）。 “Ian Jackson 是下一任 Debian 项目负责人”。 debian-announce（邮件列表）。德比安。原始存档于 2015 年 9 月 9 日。2014 年 8 月 2 日检索。
^Grobman, Igor (July 14, 1998). "debian-hurd@lists.debian.org is up!". debian-hurd (Mailing list). Debian. Archived from the original on October 18, 2018. Retrieved August 2, 2014.^ Grobman, Igor（1998 年 7 月 14 日）。 “debian-hurd@lists.debian.org 已启动！”。 debian-hurd（邮件列表）。德比安。原始存档于 2018 年 10 月 18 日。2014 年 8 月 2 日检索。
^ Jump up to: ab"Debian Voting Information". Debian. February 18, 2014. Archived from the original on June 4, 2011. Retrieved June 3, 2014.^ 跳转至： a b “Debian 投票信息”。德比安。 2014 年 2 月 18 日。原始存档于 2011 年 6 月 4 日。2014 年 6 月 3 日检索。
^Akkerman, Wichert (October 17, 1999). "New maintainer proposal". debian-project (Mailing list). Debian. Archived from the original on August 8, 2014. Retrieved August 2, 2014.^ Akkerman, Wichert（1999 年 10 月 17 日）。 “新维护者提案”。 debian-project（邮件列表）。德比安。原始存档于 2014 年 8 月 8 日。2014 年 8 月 2 日检索。
^Lohner, Nils (November 9, 1999). "New Linux distribution brings Debian to the desktop". debian-commercial (Mailing list). Debian. Archived from the original on September 9, 2015. Retrieved August 2, 2014.^ Lohner, Nils（1999 年 11 月 9 日）。 “新的 Linux 发行版将 Debian 带入桌面”。 debian-commercial（邮件列表）。德比安。原始存档于 2015 年 9 月 9 日。2014 年 8 月 2 日检索。
^Lettice, John (July 23, 2002). "Debian GNU/Linux 3.0 released". The Register. Archived from the original on July 3, 2017. Retrieved August 19, 2014.^ Lettice, John（2002 年 7 月 23 日）。 “Debian GNU/Linux 3.0 发布”。寄存器。原始存档于 2017 年 7 月 3 日。2014 年 8 月 19 日检索。
^LeMay, Renai (March 18, 2005). "Debian leaders: Faster release cycle required". ZDNet. Archived from the original on August 8, 2014. Retrieved August 3, 2014.^ LeMay, Renai（2005 年 3 月 18 日）。 “Debian 领导者：需要更快的发布周期”。 ZD网。原始存档于 2014 年 8 月 8 日。2014 年 8 月 3 日检索。
^"Ubuntu vs. Debian, reprise". Ian Murdock. April 20, 2005. Archived from the original on August 19, 2014. Retrieved June 5, 2014.^ “Ubuntu vs. Debian，再版”。伊恩·默多克。 2005 年 4 月 20 日。原始存档于 2014 年 8 月 19 日。2014 年 6 月 5 日检索。
^Verhelst, Wouter (August 21, 2005). "Results of the meeting in Helsinki about the Vancouver proposal". debian-devel-announce (Mailing list). Debian. Archived from the original on August 8, 2014. Retrieved August 3, 2014.^ Verhelst, Wouter（2005 年 8 月 21 日）。 “关于温哥华提案的赫尔辛基会议结果”。 debian-devel-announce（邮件列表）。德比安。原始存档于 2014 年 8 月 8 日。2014 年 8 月 3 日检索。
^Langasek, Steve (March 14, 2005). "Bits (Nybbles?) from the Vancouver release team meeting". debian-devel-announce (Mailing list). Debian. Archived from the original on August 8, 2014. Retrieved August 3, 2014.^ Langasek, Steve（2005 年 3 月 14 日）。 “来自温哥华发布团队会议的 Bits（Nybbles？）”。 debian-devel-announce（邮件列表）。德比安。原始存档于 2014 年 8 月 8 日。2014 年 8 月 3 日检索。
^Coleman 2013, pp. 153–154.^ Coleman 2013，第 153–154 页。
^Jarno, Aurélien (March 14, 2005). "Re: Bits (Nybbles?) from the Vancouver release team meeting". debian-devel (Mailing list). Debian. Archived from the original on August 8, 2014. Retrieved August 3, 2014.^ Jarno, Aurélien（2005 年 3 月 14 日）。 “回复：来自温哥华发布团队会议的 Bits（Nybbles？）”。 debian-devel（邮件列表）。德比安。原始存档于 2014 年 8 月 8 日。2014 年 8 月 3 日检索。
^Blache, Julien (March 14, 2005). "Re: Bits (Nybbles?) from the Vancouver release team meeting". debian-devel (Mailing list). Debian. Archived from the original on August 8, 2014. Retrieved August 3, 2014.^ Blache, Julien（2005 年 3 月 14 日）。 “回复：来自温哥华发布团队会议的 Bits（Nybbles？）”。 debian-devel（邮件列表）。德比安。原始存档于 2014 年 8 月 8 日。2014 年 8 月 3 日检索。
^Kerner, Sean Michael (April 7, 2010). "Ubuntu Claims 12 Million Users as Lucid Linux Desktop Nears". LinuxPlanet.com. Archived from the original on April 10, 2010. Retrieved April 7, 2010.^ Kerner, Sean Michael（2010 年 4 月 7 日）。 “随着 Lucid Linux 桌面的临近，Ubuntu 声称拥有 1200 万用户”。 LinuxPlanet.com。原始存档于 2010 年 4 月 10 日。2010 年 4 月 7 日检索。
^"About Ubuntu Insights". Insights.Ubuntu.com. Canonical Ltd. Archived from the original on September 6, 2015.^ “关于 Ubuntu Insights”。 Insights.Ubuntu.com。 Canonical Ltd. 原始存档于 2015 年 9 月 6 日。
^Murdock, Ian (April 20, 2005). "Ubuntu vs. Debian, reprise". Archived from the original on August 19, 2014. Retrieved October 21, 2007.^ 默多克，伊恩（2005 年 4 月 20 日）。 “Ubuntu vs. Debian，重演”。原始存档于 2014 年 8 月 19 日。2007 年 10 月 21 日检索。
^"Chapter 2 – What's new in Debian GNU/Linux 3.1". Release Notes for Debian GNU/Linux 3.1 (`sarge'), Intel x86. Debian. September 18, 2006. Archived from the original on May 19, 2010. Retrieved August 5, 2010.^ “第 2 章 – Debian GNU/Linux 3.1 的新特性”。 Debian GNU/Linux 3.1 (`sarge'), Intel x86 发行说明。德比安。 2006 年 9 月 18 日。原始存档于 2010 年 5 月 19 日。2010 年 8 月 5 日检索。
^Sanchez, Roberto C. (October 15, 2006). "Re: Will IceWeasel be based on a fork or on vanilla FireFox?". debian-devel (Mailing list). Debian. Archived from the original on August 8, 2014. Retrieved August 3, 2014.^ Sanchez, Roberto C.（2006 年 10 月 15 日）。 “回复：IceWeasel 是基于叉子还是香草 FireFox？”。 debian-devel（邮件列表）。德比安。原始存档于 2014 年 8 月 8 日。2014 年 8 月 3 日检索。
^"Debian GNU/Linux 6.0 'Squeeze' release goals". Debian. July 30, 2009. Archived from the original on March 3, 2011. Retrieved December 1, 2009.^ “Debian GNU/Linux 6.0 'Squeeze' 发布目标”。德比安。 2009 年 7 月 30 日。原始存档于 2011 年 3 月 3 日。2009 年 12 月 1 日检索。
^ Jump up to: ab"Backports service becoming official". Debian. September 5, 2010. Archived from the original on September 3, 2011. Retrieved June 17, 2014.^ 跳转至： a b “Backports 服务成为官方”。德比安。 2010 年 9 月 5 日。原始存档于 2011 年 9 月 3 日。2014 年 6 月 17 日检索。
^ Jump up to: ab"Debian 6.0 'Squeeze' released". Debian. February 6, 2011. Archived from the original on February 21, 2011. Retrieved February 6, 2011.^ 跳转至： a b “Debian 6.0 'Squeeze' 发布”。德比安。 2011 年 2 月 6 日。原始存档于 2011 年 2 月 21 日。2011 年 2 月 6 日检索。
^"Debian 7.0 'Wheezy' released". Debian. May 4, 2013. Archived from the original on December 22, 2015. Retrieved May 5, 2013.^ “Debian 7.0 'Wheezy' 发布”。德比安。 2013 年 5 月 4 日。原始存档于 2015 年 12 月 22 日。2013 年 5 月 5 日检索。
^"Debian 8 'Jessie' Released". Debian. April 25, 2015. Archived from the original on June 18, 2017. Retrieved October 27, 2015.^ “Debian 8 'Jessie' 发布”。德比安。 2015 年 4 月 25 日。原始存档于 2017 年 6 月 18 日。2015 年 10 月 27 日检索。
^"Debian 9.0 'Stretch' released". Debian. June 17, 2017. Archived from the original on June 18, 2017. Retrieved June 25, 2017.^ “Debian 9.0 'Stretch' 发布”。德比安。 2017 年 6 月 17 日。原始存档于 2017 年 6 月 18 日。2017 年 6 月 25 日检索。
^"Debian 9's release date". DistroWatch. May 26, 2017. Archived from the original on July 11, 2018. Retrieved July 11, 2018.^ “Debian 9 的发布日期”。 DistroWatch。 2017 年 5 月 26 日。原始存档于 2018 年 7 月 11 日。检索于 2018 年 7 月 11 日。
^"Debian 10.0 'buster' released". Debian. July 6, 2019. Archived from the original on July 7, 2019. Retrieved July 30, 2019.^ “Debian 10.0 'buster' 发布”。德比安。 2019 年 7 月 6 日。原始存档于 2019 年 7 月 7 日。检索于 2019 年 7 月 30 日。
^"Debian 11 'bullseye' released". Debian. August 14, 2021. Archived from the original on August 14, 2021. Retrieved August 14, 2021.^ “Debian 11 'bullseye' 发布”。德比安。 2021 年 8 月 14 日。原始存档于 2021 年 8 月 14 日。2021 年 8 月 14 日检索。
^"Chapter 2. What's new in Debian 9". www.debian.org. Archived from the original on March 8, 2021. Retrieved July 2, 2020.^ “第 2 章。Debian 9 中的新功能”。 www.debian.org。原始存档于 2021 年 3 月 8 日。2020 年 7 月 2 日检索。
^"Awards". Debian. Archived from the original on November 20, 2008. Retrieved November 2, 2008.^ “奖项”。德比安。原始存档于 2008 年 11 月 20 日。2008 年 11 月 2 日检索。
^"The best Linux distro of 2011!". TuxRadar. August 4, 2011. Archived from the original on June 6, 2014. Retrieved June 6, 2014.^ “2011 年最佳 Linux 发行版！”。塔克斯雷达。 2011 年 8 月 4 日。原始存档于 2014 年 6 月 6 日。2014 年 6 月 6 日检索。
^"debian-devel". Debian. Archived from the original on February 13, 2016. Retrieved February 8, 2016.^ “debian-开发”。德比安。原始存档于 2016 年 2 月 13 日。2016 年 2 月 8 日检索。
^ Jump up to: ab"Debian – Packages". Debian. Archived from the original on June 21, 2014. Retrieved June 22, 2014.^ 跳转至： a b “Debian – 软件包”。德比安。原始存档于 2014 年 6 月 21 日。2014 年 6 月 22 日检索。
^"Debian Moves to LibreOffice". Debian. Archived from the original on January 11, 2012. Retrieved March 5, 2012.^ “Debian 迁移到 LibreOffice”。德比安。原始存档于 2012 年 1 月 11 日。2012 年 3 月 5 日检索。
^Noyes, Katherine (January 11, 2012). "Debian Linux Named Most Popular Distro for Web Servers". PC World. Archived from the original on February 9, 2013. Retrieved February 14, 2013.^ Noyes, Katherine（2012 年 1 月 11 日）。 “Debian Linux 被评为 Web 服务器最受欢迎的发行版”。电脑世界。原始存档于 2013 年 2 月 9 日。2013 年 2 月 14 日检索。
^"Virtual Package: linux-image". Debian. Archived from the original on August 19, 2014. Retrieved August 15, 2014.^ “虚拟包：linux-image”。德比安。原始存档于 2014 年 8 月 19 日。2014 年 8 月 15 日检索。
^"Chapter 2 – Debian kernel source". Debian Linux Kernel Handbook. Alioth. December 14, 2013. Archived from the original on June 4, 2014. Retrieved August 15, 2014.^ “第 2 章 – Debian 内核源代码”。 Debian Linux 内核手册。阿里奥特。 2013 年 12 月 14 日。原始存档于 2014 年 6 月 4 日。2014 年 8 月 15 日检索。
^"Debian – Details of package cinnamon in jessie". packages.debian.org. Archived from the original on September 9, 2015. Retrieved September 6, 2015.^ “Debian – jessie 中 cinnamon 包的详细信息”。 packages.debian.org。原始存档于 2015 年 9 月 9 日。2015 年 9 月 6 日检索。
^"Virtual Package: x-window-manager". Debian. Archived from the original on May 27, 2014. Retrieved May 27, 2014.^ “虚拟包：x-window-manager”。德比安。原始存档于 2014 年 5 月 27 日。2014 年 5 月 27 日检索。
^"Debian Installer Buster RC 3 release". Debian. July 3, 2019. Archived from the original on August 23, 2019. Retrieved August 22, 2019.^ “Debian 安装程序 Buster RC 3 发布”。德比安。 2019 年 7 月 3 日。原始存档于 2019 年 8 月 23 日。检索于 2019 年 8 月 22 日。
^Mejia, Andres (March 18, 2012). "Diff for 'MultimediaCodecs'". Debian Wiki. Archived from the original on October 20, 2014. Retrieved October 16, 2014.^ Mejia, Andres（2012 年 3 月 18 日）。 ““多媒体编解码器”的差异”。 Debian 维基百科。原始存档于 2014 年 10 月 20 日。2014 年 10 月 16 日检索。
^"RFP: libdvdcss – Library to read scrambled DVDs". Debian BTS. July 25, 2002. Archived from the original on December 2, 2018. Retrieved July 9, 2014.^ “RFP：libdvdcss – 读取加扰 DVD 的库”。 Debian 防弹少年团。 2002 年 7 月 25 日。原始存档于 2018 年 12 月 2 日。2014 年 7 月 9 日检索。
^Gilbertson, Scott (February 16, 2009). "'Lenny': Debian for the masses?". The Register. Archived from the original on August 10, 2017. Retrieved July 13, 2014.^ Gilbertson, Scott（2009 年 2 月 16 日）。 “'Lenny'：面向大众的 Debian？”。寄存器。原始存档于 2017 年 8 月 10 日。2014 年 7 月 13 日检索。
^Granneman, Scott (February 6, 2008). "Cool APT Repositories for Ubuntu and Debian". Linux Magazine. Archived from the original on July 14, 2014. Retrieved July 13, 2014.: CS1 maint: unfit URL ()^ Granneman, Scott（2008 年 2 月 6 日）。 “适用于 Ubuntu 和 Debian 的酷 APT 存储库”。 Linux 杂志。原始存档于 2014 年 7 月 14 日。2014 年 7 月 13 日检索。
^Nestor, Marius (March 19, 2012). "Window Maker Live CD 2012-03-18 Available for Download". Softpedia. Archived from the original on November 29, 2014. Retrieved November 22, 2014.^ Nestor, Marius（2012 年 3 月 19 日）。 “Window Maker Live CD 2012-03-18 可供下载”。软百科。原始存档于 2014 年 11 月 29 日。2014 年 11 月 22 日检索。
^"Packages". deb-multimedia.org. Archived from the original on July 14, 2014. Retrieved July 13, 2014.^ “包裹”。 deb-multimedia.org。原始存档于 2014 年 7 月 14 日。2014 年 7 月 13 日检索。
^"Debian on CDs". Debian. May 10, 2014. Archived from the original on August 7, 2011. Retrieved May 27, 2014.^ “CD 上的 Debian”。德比安。 2014 年 5 月 10 日。原始存档于 2011 年 8 月 7 日。2014 年 5 月 27 日检索。
^ Jump up to: ab"6.3. Using Individual Components". Debian GNU/Linux Installation Guide. Debian. 2013. Archived from the original on December 24, 2013. Retrieved 2014-05-30.^ 跳转至：a b “6.3. 使用独立组件”。 Debian GNU/Linux 安装指南。德比安。 2013。原始存档于 2013 年 12 月 24 日。于 2014-05-30 检索。
^Watson, J.A. (May 28, 2013). "Debian Linux 7.0 Wheezy: Hands on". ZDNet. Archived from the original on May 1, 2014. Retrieved June 10, 2014. For the CD images, it is useful to know that Debian supports a number of different desktops, including GNOME, KDE, Xfce, MATE and LXDE, and there is a different 'disk 1' image for each of these desktops.^ 沃森，J.A. （2013 年 5 月 28 日）。 “Debian Linux 7.0 Wheezy：动手”。 ZD网。原始存档于 2014 年 5 月 1 日。检索于 2014 年 6 月 10 日。对于 CD 映像，知道 Debian 支持许多不同的桌面是很有用的，包括 GNOME、KDE、Xfce、MATE 和 LXDE，并且有一个每个桌面都有不同的“磁盘 1”映像。
^"Live install images". Debian. October 27, 2013. Archived from the original on June 7, 2017. Retrieved December 7, 2013.^ “实时安装图像”。德比安。 2013 年 10 月 27 日。原始存档于 2017 年 6 月 7 日。2013 年 12 月 7 日检索。
^"Debian Live Manual". Debian. 2013. Archived from the original on February 14, 2014. Retrieved 2014-07-06.^ “Debian Live 手册”。德比安。 2013。原始存档于 2014 年 2 月 14 日。检索 2014-07-06。
^"4.3. Preparing Files for USB Memory Stick Booting". Debian GNU/Linux Installation Guide. Debian. 2010. Archived from the original on May 27, 2014. Retrieved May 27, 2014.^ “4.3. 准备U盘启动文件”。 Debian GNU/Linux 安装指南。德比安。 2010。原始存档于 2014 年 5 月 27 日。2014 年 5 月 27 日检索。
^ Jump up to: abcd"Chapter 2. Debian package management". Debian Reference. Debian. December 3, 2013. Archived from the original on August 8, 2011. Retrieved May 29, 2014.^ 跳转至：a b c d “第 2 章 Debian 软件包管理”。 Debian 参考。德比安。 2013 年 12 月 3 日。原始存档于 2011 年 8 月 8 日。2014 年 5 月 29 日检索。
^"Package: synaptic (0.75.13)". Debian. Archived from the original on July 6, 2014. Retrieved June 19, 2014.^“包：突触（0.75.13）”。德比安。原始存档于 2014 年 7 月 6 日。2014 年 6 月 19 日检索。
^"Package: apper (0.7.2-5)". Debian. Archived from the original on July 6, 2014. Retrieved June 19, 2014.^ “包：apper (0.7.2-5)”。德比安。原始存档于 2014 年 7 月 6 日。2014 年 6 月 19 日检索。
^ Jump up to: abcd"Debian Social Contract". Debian. Archived from the original on February 17, 2011. Retrieved June 17, 2013.^ 跳转至：a b c d “Debian 社会契约”。德比安。原始存档于 2011 年 2 月 17 日。2013 年 6 月 17 日检索。
^"License information". Debian. Archived from the original on July 20, 2017. Retrieved February 28, 2009.^ “许可证信息”。德比安。原始存档于 2017 年 7 月 20 日。2009 年 2 月 28 日检索。
^ Jump up to: abc"Chapter 2 – The Debian Archive". Debian Policy Manual. Debian. October 28, 2013. Archived from the original on July 13, 2014. Retrieved July 9, 2014.^ 跳转至：a b c “第 2 章 – Debian 档案库”。 Debian 政策手册。德比安。 2013 年 10 月 28 日。原始存档于 2014 年 7 月 13 日。2014 年 7 月 9 日检索。
^Stallman, Richard (October 6, 2007). "Re: Debian vs gNewSense – FS criteria". gnuherds-app-dev (Mailing list). lists.nongnu.org. Archived from the original on July 14, 2014. Retrieved July 9, 2014. What makes Debian unacceptable is that its inclusion of non-free software is not a mistake.^ Stallman, Richard（2007 年 10 月 6 日）。 “回复：Debian vs gNewSense – FS 标准”。 gnuherds-app-dev（邮件列表）。 lists.nongnu.org.原始存档于 2014 年 7 月 14 日。检索于 2014 年 7 月 9 日。让 Debian 无法接受的是它包含非自由软件并不是一个错误。
^Akkerman, Wichert (June 21, 1999). "Moving contrib and non-free of master.debian.org". debian-vote (Mailing list). Debian. Archived from the original on July 20, 2014. Retrieved August 4, 2014.^ Akkerman, Wichert（1999 年 6 月 21 日）。 “移动 contrib 和 non-free of master.debian.org”。 debian-vote（邮件列表）。德比安。原始存档于 2014 年 7 月 20 日。2014 年 8 月 4 日检索。
^Wise, Paul (March 22, 2014). "non-free?". debian-vote (Mailing list). Debian. Archived from the original on August 19, 2014. Retrieved August 16, 2014.^ Wise, Paul（2014 年 3 月 22 日）。 “非免费的？”。 debian-vote（邮件列表）。德比安。原始存档于 2014 年 8 月 19 日。2014 年 8 月 16 日检索。
^ Jump up to: ab"How to Install and Use Flatpak on Linux". Linux Today. November 27, 2020. Archived from the original on December 18, 2021. Retrieved December 19, 2021.^ 跳转至：a b “如何在 Linux 上安装和使用 Flatpak”。今天的Linux。 2020 年 11 月 27 日。原始存档于 2021 年 12 月 18 日。检索于 2021 年 12 月 19 日。
^ Jump up to: ab"Debian Releases". Debian. Archived from the original on October 11, 2011. Retrieved June 22, 2014.^ 跳转至： a b “Debian 发行版”。德比安。原始存档于 2011 年 10 月 11 日。2014 年 6 月 22 日检索。
^Vaughan-Nichols, Steven J. (May 5, 2013). "The new Debian Linux 7.0 is now available". ZDNet. Archived from the original on November 29, 2014. Retrieved July 8, 2014.^ Vaughan-Nichols, Steven J.（2013 年 5 月 5 日）。 “新的 Debian Linux 7.0 现已推出”。 ZD网。原始存档于 2014 年 11 月 29 日。2014 年 7 月 8 日检索。
^"Frequently Asked Questions". Debian. Archived from the original on July 14, 2014. Retrieved July 9, 2014.^ “常见问题”。德比安。原始存档于 2014 年 7 月 14 日。2014 年 7 月 9 日检索。
^ Jump up to: abc"Debian security FAQ". Debian. February 28, 2007. Archived from the original on August 28, 2008. Retrieved October 21, 2008.^ 跳转至：a b c “Debian 安全常见问题解答”。德比安。 2007 年 2 月 28 日。原始存档于 2008 年 8 月 28 日。2008 年 10 月 21 日检索。
^"snapshot.debian.org". Debian. Archived from the original on June 13, 2019. Retrieved July 9, 2014.^ “snapshot.debian.org”。德比安。原始存档于 2019 年 6 月 13 日。2014 年 7 月 9 日检索。
^"ChangeLog". bullseye. Debian. February 6, 2021. Archived from the original on August 14, 2021. Retrieved August 14, 2021.^ “变更日志”。靶心。德比安。 2021 年 2 月 6 日。原始存档于 2021 年 8 月 14 日。2021 年 8 月 14 日检索。
^"ChangeLog". buster. Debian. August 14, 2021. Archived from the original on August 14, 2021. Retrieved August 14, 2021.^ “变更日志”。克星。德比安。 2021 年 8 月 14 日。原始存档于 2021 年 8 月 14 日。2021 年 8 月 14 日检索。
^"Release". etch. Debian. May 22, 2010. Archived from the original on August 15, 2015. Retrieved June 5, 2014.^ “发布”。蚀刻。德比安。 2010 年 5 月 22 日。原始存档于 2015 年 8 月 15 日。2014 年 6 月 5 日检索。
^Schulze, Martin (August 24, 1998). "Naming of new 2.0 release". debian-devel (Mailing list). Debian. Archived from the original on July 28, 2014. Retrieved July 26, 2014.^ 舒尔茨，马丁（1998 年 8 月 24 日）。 “新 2.0 版本的命名”。 debian-devel（邮件列表）。德比安。原始存档于 2014 年 7 月 28 日。2014 年 7 月 26 日检索。
^"GNU Coding Standards: Releases". GNU. May 13, 2014. Archived from the original on May 25, 2014. Retrieved May 25, 2014. You should identify each release with a pair of version numbers, a major version and a minor. We have no objection to using more than two numbers, but it is very unlikely that you really need them.^ “GNU 编码标准：发布”。 GNU。 2014 年 5 月 13 日。从 2014 年 5 月 25 日的原始版本存档。2014 年 5 月 25 日检索。您应该使用一对版本号（主要版本和次要版本）来标识每个版本。我们不反对使用两个以上的数字，但您不太可能真的需要它们。
^Brockschmidt, Marc (February 15, 2009). "Debian squeeze waiting for development". debian-devel-announce (Mailing list). Debian. Archived from the original on June 20, 2017. Retrieved February 15, 2009.^ Brockschmidt, Marc（2009 年 2 月 15 日）。 “Debian 挤压等待开发”。 debian-devel-announce（邮件列表）。德比安。原始存档于 2017 年 6 月 20 日。2009 年 2 月 15 日检索。
^"ChangeLog". wheezy. Debian. June 4, 2016. Archived from the original on July 4, 2014. Retrieved December 14, 2016.^ “变更日志”。气喘吁吁的。德比安。 2016 年 6 月 4 日。原始存档于 2014 年 7 月 4 日。2016 年 12 月 14 日检索。
^"Updated Debian 7: 7.7 released". Debian. October 18, 2014. Archived from the original on October 25, 2014. Retrieved October 20, 2014.^ “更新的 Debian 7：7.7 发布”。德比安。 2014 年 10 月 18 日。原始存档于 2014 年 10 月 25 日。2014 年 10 月 20 日检索。
^Vaughan-Nichols, Steven J. (December 16, 2009). "The Five Distros That Changed Linux". Linux Magazine. Archived from the original on June 16, 2013. Retrieved February 14, 2013.: CS1 maint: unfit URL ()^ Vaughan-Nichols, Steven J.（2009 年 12 月 16 日）。 “改变 Linux 的五个发行版”。 Linux 杂志。原始存档于 2013 年 6 月 16 日。2013 年 2 月 14 日检索。
^ Jump up to: ab"Chapter 2. What are Debian Pure Blends?". Debian Pure Blends. Debian. Archived from the original on May 27, 2014. Retrieved May 27, 2014.^ 跳转至： a b “第 2 章。什么是 Debian Pure Blends？”。 Debian 纯混合。德比安。原始存档于 2014 年 5 月 27 日。2014 年 5 月 27 日检索。
^"Debian Jr. Project". Debian. April 30, 2014. Archived from the original on October 11, 2011. Retrieved June 16, 2014.^ “Debian Jr. 项目”。德比安。 2014 年 4 月 30 日。原始存档于 2011 年 10 月 11 日。2014 年 6 月 16 日检索。
^Armstrong, Ben (July 6, 2011). "Re: Difference between blends and remastered systems". debian-blends (Mailing list). Debian. Archived from the original on July 6, 2014. Retrieved June 16, 2014.^ Armstrong, Ben（2011 年 7 月 6 日）。 “回复：混合系统和重制系统之间的区别”。 debian-blends（邮件列表）。德比安。原始存档于 2014 年 7 月 6 日。2014 年 6 月 16 日检索。
^Wiltshire, Jonathan (November 9, 2014). "Release Team Sprint Results". debian-devel-announce (Mailing list). Archived from the original on February 21, 2018. Retrieved January 10, 2017.^ 乔纳森·威尔特郡（2014 年 11 月 9 日）。 “发布团队冲刺结果”。 debian-devel-announce（邮件列表）。原始存档于 2018 年 2 月 21 日。2017 年 1 月 10 日检索。
^Garrett, Matthew (January 6, 2002). "Chrooted NetBSD environment available for testing". debian-bsd (Mailing list). Archived from the original on September 6, 2015. Retrieved December 17, 2019.^ Garrett, Matthew（2002 年 1 月 6 日）。 “可用于测试的 Chrooted NetBSD 环境”。 debian-bsd（邮件列表）。原始存档于 2015 年 9 月 6 日。检索于 2019 年 12 月 17 日。
^"Debian_GNU/kFreeBSD_why". Debian Wiki. October 5, 2011. Archived from the original on February 22, 2017. Retrieved July 5, 2013.^ “Debian_GNU/kFreeBSD_why”。 Debian 维基百科。 2011 年 10 月 5 日。原始存档于 2017 年 2 月 22 日。2013 年 7 月 5 日检索。
^"Debian GNU/kFreeBSD". Debian.org. Archived from the original on May 31, 2014. Retrieved May 26, 2014.^ “Debian GNU/kFreeBSD”。 Debian.org。原始存档于 2014 年 5 月 31 日。2014 年 5 月 26 日检索。
^"debian-bsd Jul 2019 by thread". lists.debian.org. Archived from the original on July 31, 2019. Retrieved July 31, 2019.^ “debian-bsd 2019 年 7 月通过线程”。 lists.debian.org.原始存档于 2019 年 7 月 31 日。2019 年 7 月 31 日检索。
^"debian-hurd@lists.debian.org is up!" (Mailing list). Archived from the original on October 18, 2018. Retrieved September 10, 2009.^ “debian-hurd@lists.debian.org 已启动！” （邮件列表）。原始存档于 2018 年 10 月 18 日。2009 年 9 月 10 日检索。
^"News about Debian GNU/Hurd". Archived from the original on December 5, 1999. Retrieved August 17, 2021.^ “关于 Debian GNU/Hurd 的新闻”。原始存档于 1999 年 12 月 5 日。2021 年 8 月 17 日检索。
^"GNU/art". Archived from the original on February 8, 2015. Retrieved February 18, 2015.^ “GNU/艺术”。原始存档于 2015 年 2 月 8 日。2015 年 2 月 18 日检索。
^"Logo credit". Archived from the original on February 18, 2015. Retrieved February 18, 2015.^ “标志信用”。原始存档于 2015 年 2 月 18 日。2015 年 2 月 18 日检索。
^"Debian Logo Contest". Archived from the original on February 18, 2015. Retrieved March 24, 2021.^ “Debian 标志大赛”。原始存档于 2015 年 2 月 18 日。2021 年 3 月 24 日检索。
^"Origins of the Debian logo". Archived from the original on January 12, 2018. Retrieved January 11, 2018.^ “Debian 标志的起源”。原始存档于 2018 年 1 月 12 日。2018 年 1 月 11 日检索。
^Toy Story (Billboard). Pixar. Archived from the original on November 10, 2013. Retrieved August 20, 2014.^ 玩具总动员（广告牌）。皮克斯。原始存档于 2013 年 11 月 10 日。2014 年 8 月 20 日检索。
^ Jump up to: ab"2.1. Supported Hardware". Debian GNU/Linux Installation Guide. Debian. 2019. Archived from the original on December 28, 2020. Retrieved July 27, 2019.^ 跳转至：a b “2.1. 支持的硬件”。 Debian GNU/Linux 安装指南。德比安。 2019。原始存档于 2020 年 12 月 28 日。检索于 2019 年 7 月 27 日。
^ Jump up to: abcde"3.4. Meeting Minimum Hardware Requirements". Debian GNU/Linux Installation Guide. Debian. 2019. Archived from the original on January 12, 2021. Retrieved July 27, 2019.^ 跳转至： a b c d e “3.4. 满足最低硬件要求”。 Debian GNU/Linux 安装指南。德比安。 2019。原始存档于 2021 年 1 月 12 日。检索于 2019 年 7 月 27 日。
^"5.1. Booting the Installer on S/390". Debian GNU/Linux Installation Guide. Debian. 2015. Archived from the original on July 29, 2020. Retrieved January 20, 2017.^ “5.1. 在 S/390 上引导安装程序”。 Debian GNU/Linux 安装指南。德比安。 2015 年。原始存档于 2020 年 7 月 29 日。2017 年 1 月 20 日检索。
^"Chapter 4. Existing Debian Pure Blends". Debian Pure Blends. Debian. June 19, 2013. Archived from the original on May 28, 2014. Retrieved June 19, 2014.^ “第 4 章。现有的 Debian Pure Blends”。 Debian 纯混合。德比安。 2013 年 6 月 19 日。原始存档于 2014 年 5 月 28 日。2014 年 6 月 19 日检索。
^ Jump up to: abWookey (August 27, 2014). "Two new architectures bootstrapping in unstable – MBF coming soon". debian-devel-announce (Mailing list). Debian. Archived from the original on September 3, 2014. Retrieved September 1, 2014.^ 跳转至：a b Wookey（2014 年 8 月 27 日）。 “两个新的架构在 unstable 中启动——MBF 即将推出”。 debian-devel-announce（邮件列表）。德比安。原始存档于 2014 年 9 月 3 日。2014 年 9 月 1 日检索。
^Wookey (January 23, 2010). "Re: Identification of ARM chips". debian-embedded (Mailing list). Debian. Archived from the original on October 21, 2014. Retrieved October 16, 2014.^ Wookey（2010 年 1 月 23 日）。 “回复：ARM 芯片的识别”。 debian-embedded（邮件列表）。德比安。原始存档于 2014 年 10 月 21 日。2014 年 10 月 16 日检索。
^"Chapter 2. What's new in Debian 7.0". Release Notes for Debian 7.0 (wheezy), S/390. November 9, 2014. Archived from the original on December 25, 2013. Retrieved January 28, 2015.^ “第 2 章。Debian 7.0 中的新功能”。 Debian 7.0 (wheezy), S/390 发行说明。 2014 年 11 月 9 日。原始存档于 2013 年 12 月 25 日。2015 年 1 月 28 日检索。
^Schepler, Daniel (November 20, 2012). "X32Port". Debian Wiki. Archived from the original on October 21, 2014. Retrieved October 17, 2014.^ Schepler, Daniel（2012 年 11 月 20 日）。 “X32端口”。 Debian 维基百科。原始存档于 2014 年 10 月 21 日。2014 年 10 月 17 日检索。
^Brown, Silas. "Upgrading your Slug LG #161". Linux Gazette. Archived from the original on December 16, 2010. Retrieved July 27, 2011.^ 布朗，西拉斯。 “升级您的 Slug LG #161”。 Linux 公报。原始存档于 2010 年 12 月 16 日。2011 年 7 月 27 日检索。
^"Installing Debian on NSLU2". Martin Michlmayr. February 24, 2011. Archived from the original on May 31, 2014. Retrieved July 27, 2011.^ “在 NSLU2 上安装 Debian”。马丁·米歇尔迈尔。 2011 年 2 月 24 日。原始存档于 2014 年 5 月 31 日。2011 年 7 月 27 日检索。
^ Jump up to: ab"Chapter 2. What's new in Debian GNU/Linux 5.0". Release Notes for Debian GNU/Linux 5.0 (lenny), ARM. Debian. Archived from the original on June 28, 2011. Retrieved July 27, 2011.^ 跳转至： a b “第 2 章。Debian GNU/Linux 5.0 的新特性”。 Debian GNU/Linux 5.0 (lenny)、ARM 发行说明。德比安。原始存档于 2011 年 6 月 28 日。2011 年 7 月 27 日检索。
^"Chapter 2 – What's new in Debian GNU/Linux 4.0". Release Notes for Debian GNU/Linux 4.0 ('etch'), ARM. Debian. August 16, 2007. Archived from the original on June 28, 2011. Retrieved July 27, 2011.^ “第 2 章 – Debian GNU/Linux 4.0 的新特性”。 Debian GNU/Linux 4.0 ('etch'), ARM 发行说明。德比安。 2007 年 8 月 16 日。原始存档于 2011 年 6 月 28 日。2011 年 7 月 27 日检索。
^"Chapter 2. What's new in Debian GNU/Linux 6.0". Release Notes for Debian GNU/Linux 6.0 (squeeze), ARM EABI. Debian. Archived from the original on November 9, 2020. Retrieved July 27, 2011.^ “第 2 章。Debian GNU/Linux 6.0 的新特性”。 Debian GNU/Linux 6.0 (squeeze)、ARM EABI 发行说明。德比安。原始存档于 2020 年 11 月 9 日。2011 年 7 月 27 日检索。
^"Debian Project News – December 10th, 2012". Debian. December 10, 2012. Archived from the original on July 6, 2014. Retrieved June 17, 2014.^ “Debian 项目新闻 – 2012 年 12 月 10 日”。德比安。 2012 年 12 月 10 日。原始存档于 2014 年 7 月 6 日。2014 年 6 月 17 日检索。
^"Package: matchbox (1:5)". Debian. Archived from the original on July 6, 2014. Retrieved June 17, 2014.^ “包装：火柴盒 (1:5)”。德比安。原始存档于 2014 年 7 月 6 日。2014 年 6 月 17 日检索。
^Hess, Joey (September 23, 2005). "DebianWRT". Debian Wiki. Archived from the original on October 21, 2014. Retrieved October 17, 2014.^ Hess, Joey（2005 年 9 月 23 日）。 “DebianWRT”。 Debian 维基百科。原始存档于 2014 年 10 月 21 日。2014 年 10 月 17 日检索。
^"Debian Project News – December 2nd, 2013". Debian. December 2, 2013. Archived from the original on July 6, 2014. Retrieved June 17, 2014.^ “Debian 项目新闻 – 2013 年 12 月 2 日”。德比安。 2013 年 12 月 2 日。原始存档于 2014 年 7 月 6 日。2014 年 6 月 17 日检索。
^Liu, Ying-Chun (January 27, 2012). "InstallingDebianOn TI BeagleBone". Debian Wiki. Archived from the original on October 21, 2014. Retrieved October 17, 2014.^ 刘迎春（2012 年 1 月 27 日）。 “在 TI BeagleBone 上安装 Debian”。 Debian 维基百科。原始存档于 2014 年 10 月 21 日。2014 年 10 月 17 日检索。
^"Debian New Member – Status DD, upl". Debian. Archived from the original on July 6, 2014. Retrieved June 21, 2014.^ “Debian 新成员 – Status DD, upl”。德比安。原始存档于 2014 年 7 月 6 日。2014 年 6 月 21 日检索。
^"How can you help Debian?". Debian. April 30, 2014. Archived from the original on May 16, 2014. Retrieved June 3, 2014.^ “你如何帮助 Debian？”。德比安。 2014 年 4 月 30 日。原始存档于 2014 年 5 月 16 日。2014 年 6 月 3 日检索。
^"Index of /pub/debian-meetings". Debian. Archived from the original on June 14, 2018. Retrieved July 16, 2014.^ “/pub/debian-meetings 索引”。德比安。原始存档于 2018 年 6 月 14 日。2014 年 7 月 16 日检索。
^"Debian bug tracking system pseudo-packages". Debian. December 8, 2013. Archived from the original on June 6, 2014. Retrieved June 3, 2014.^ “Debian 错误跟踪系统伪软件包”。德比安。 2013 年 12 月 8 日。原始存档于 2014 年 6 月 6 日。2014 年 6 月 3 日检索。
^"Support". Debian. April 30, 2014. Archived from the original on May 28, 2014. Retrieved June 3, 2014.^ “支持”。德比安。 2014 年 4 月 30 日。原始存档于 2014 年 5 月 28 日。2014 年 6 月 3 日检索。
^"Chapter 2 – Leadership". A Brief History of Debian. Debian. May 4, 2013. Archived from the original on December 26, 2010. Retrieved July 5, 2014.^ “第 2 章 – 领导力”。 Debian 简史。德比安。 2013 年 5 月 4 日。原始存档于 2010 年 12 月 26 日。2014 年 7 月 5 日检索。
^van Wolffelaar, Jeroen (March 5, 2005). "Announcing project scud". debian-project (Mailing list). Debian. Archived from the original on July 25, 2014. Retrieved July 17, 2014.^ van Wolffelaar, Jeroen（2005 年 3 月 5 日）。 “宣布飞毛腿项目”。 debian-project（邮件列表）。德比安。原始存档于 2014 年 7 月 25 日。2014 年 7 月 17 日检索。
^"The Debian organization web page". Debian. Archived from the original on November 29, 2011. Retrieved November 1, 2008.^ “Debian 组织网页”。德比安。原始存档于 2011 年 11 月 29 日。2008 年 11 月 1 日检索。
^Towns, Anthony (March 8, 2003). "Bits from the RM: Help Wanted, Apply Within". debian-devel-announce (Mailing list). Debian. Archived from the original on July 25, 2014. Retrieved July 17, 2014.^ Towns, Anthony（2003 年 3 月 8 日）。 “来自 RM 的信息：需要帮助，在其中应用”。 debian-devel-announce（邮件列表）。德比安。原始存档于 2014 年 7 月 25 日。2014 年 7 月 17 日检索。
^"Debian New Maintainers". Debian. Archived from the original on November 20, 2008. Retrieved October 31, 2008.^ “Debian 新维护者”。德比安。原始存档于 2008 年 11 月 20 日。2008 年 10 月 31 日检索。
^Berg, Christoph (January 10, 2009). "AM report for Alexander GQ Gerasiov". debian-newmaint (Mailing list). Debian. Archived from the original on July 25, 2014. Retrieved July 18, 2014.^ Berg, Christoph（2009 年 1 月 10 日）。 “Alexander GQ Gerasiov 的 AM 报告”。 debian-newmaint（邮件列表）。德比安。原始存档于 2014 年 7 月 25 日。2014 年 7 月 18 日检索。
^Joeris, Steffen (January 3, 2010). "AM report for Jakub Wilk [...]". debian-newmaint (Mailing list). Debian. Archived from the original on July 25, 2014. Retrieved July 18, 2014.^ Joeris, Steffen（2010 年 1 月 3 日）。 “Jakub Wilk 的 AM 报告 [...]”。 debian-newmaint（邮件列表）。德比安。原始存档于 2014 年 7 月 25 日。2014 年 7 月 18 日检索。
^Wolf, Gunnar (January 13, 2011). "AM report for Kamal Mostafa". debian-newmaint (Mailing list). Debian. Archived from the original on July 25, 2014. Retrieved July 18, 2014.^ Wolf, Gunnar（2011 年 1 月 13 日）。 “Kamal Mostafa 的 AM 报告”。 debian-newmaint（邮件列表）。德比安。原始存档于 2014 年 7 月 25 日。2014 年 7 月 18 日检索。
^Faraone, Luke (January 1, 2012). "AM report for vicho". debian-newmaint (Mailing list). Debian. Archived from the original on July 25, 2014. Retrieved July 18, 2014.^ Faraone, Luke（2012 年 1 月 1 日）。 “维乔的上午报告”。 debian-newmaint（邮件列表）。德比安。原始存档于 2014 年 7 月 25 日。2014 年 7 月 18 日检索。
^Wiltshire, Jonathan (January 6, 2013). "AM report for Manuel A. Fernandez Montecelo". debian-newmaint (Mailing list). Debian. Archived from the original on July 25, 2014. Retrieved July 18, 2014.^ 乔纳森·威尔特郡（2013 年 1 月 6 日）。 “Manuel A. Fernandez Montecelo 的 AM 报告”。 debian-newmaint（邮件列表）。德比安。原始存档于 2014 年 7 月 25 日。2014 年 7 月 18 日检索。
^ Jump up to: ab"Chapter 3. Debian Developer's Duties". Debian Developer's Reference. Debian. Archived from the original on July 16, 2014. Retrieved July 19, 2014.^ 跳转至： a b “第 3 章 Debian 开发人员的职责”。 Debian 开发人员参考。德比安。原始存档于 2014 年 7 月 16 日。2014 年 7 月 19 日检索。
^"Chapter 3 – Binary packages". Debian Policy Manual. Debian. October 28, 2013. Archived from the original on August 4, 2011. Retrieved July 19, 2014.^ “第 3 章 – 二进制包”。 Debian 政策手册。德比安。 2013 年 10 月 28 日。原始存档于 2011 年 8 月 4 日。2014 年 7 月 19 日检索。
^"Chapter 2. Applying to Become a Maintainer". Debian Developer's Reference. Debian. Archived from the original on September 23, 2020. Retrieved October 9, 2010.^ “第 2 章。申请成为维护者”。 Debian 开发人员参考。德比安。原始存档于 2020 年 9 月 23 日。2010 年 10 月 9 日检索。
^Costela, Leo (February 12, 2010). "DebianMentorsFaq". Debian Wiki. Archived from the original on October 21, 2014. Retrieved October 17, 2014.^ Costela, Leo（2010 年 2 月 12 日）。 “DebianMentorsFaq”。 Debian 维基百科。原始存档于 2014 年 10 月 21 日。2014 年 10 月 17 日检索。
^"Chapter 5. Managing Packages". Debian Developer's Reference. Debian. Archived from the original on January 9, 2021. Retrieved October 31, 2008.^ “第 5 章。管理包”。 Debian 开发人员参考。德比安。原始存档于 2021 年 1 月 9 日。2008 年 10 月 31 日检索。
^"Debian 'testing' distribution". Debian. Archived from the original on November 20, 2008. Retrieved November 24, 2008.^ “Debian‘测试’发行版”。德比安。原始存档于 2008 年 11 月 20 日。2008 年 11 月 24 日检索。
^McGovern, Neil (April 18, 2013). "FINAL release update". debian-devel-announce (Mailing list). Debian. Archived from the original on July 17, 2014. Retrieved July 20, 2014.^ McGovern, Neil（2013 年 4 月 18 日）。 “最终版本更新”。 debian-devel-announce（邮件列表）。德比安。原始存档于 2014 年 7 月 17 日。2014 年 7 月 20 日检索。
^"Point Releases - Debian Wiki". Debian Release Team. Archived from the original on September 25, 2019. Retrieved September 27, 2017.^ “点发布 - Debian Wiki”。 Debian 发布团队。原始存档于 2019 年 9 月 25 日。检索于 2017 年 9 月 27 日。
^"LTS - Debian Wiki". Debian LTS Team. July 3, 2018. Archived from the original on May 7, 2020. Retrieved August 18, 2018.^ “LTS - Debian 维基”。 Debian LTS 团队。 2018 年 7 月 3 日。原始存档于 2020 年 5 月 7 日。2018 年 8 月 18 日检索。
^"Security Information". Debian. Archived from the original on October 31, 2012. Retrieved December 13, 2008.^ “安全信息”。德比安。原始存档于 2012 年 10 月 31 日。2008 年 12 月 13 日检索。
^"Organizations Participating". MITRE. April 16, 2014. Archived from the original on May 26, 2014. Retrieved June 5, 2014.^ “组织参与”。斜接。 2014 年 4 月 16 日。原始存档于 2014 年 5 月 26 日。2014 年 6 月 5 日检索。
^"Debian Security Audit Project". Debian. March 15, 2014. Archived from the original on June 6, 2014. Retrieved June 4, 2014.^ “Debian 安全审计项目”。德比安。 2014 年 3 月 15 日。原始存档于 2014 年 6 月 6 日。2014 年 6 月 4 日检索。
^"Advisories". Steve Kemp. Archived from the original on August 19, 2014. Retrieved August 18, 2014.^ “忠告”。史蒂夫·坎普。原始存档于 2014 年 8 月 19 日。2014 年 8 月 18 日检索。
^"Steve Kemp". Debian. Archived from the original on August 19, 2014. Retrieved August 18, 2014.^ “史蒂夫·坎普”。德比安。原始存档于 2014 年 8 月 19 日。2014 年 8 月 18 日检索。
^"Securing Debian Manual". Debian. Archived from the original on January 28, 2021. Retrieved December 13, 2008.^ “保护 Debian 手册”。德比安。原始存档于 2021 年 1 月 28 日。2008 年 12 月 13 日检索。
^"Debian -- News -- Debian 10 "buster" released". www.debian.org. Archived from the original on July 7, 2019. Retrieved July 8, 2019.^ “Debian -- 新闻 -- Debian 10 “克星”发布”。 www.debian.org。原始存档于 2019 年 7 月 7 日。2019 年 7 月 8 日检索。
^"Debian Secure by Default". Debian: SbD. Archived from the original on November 3, 2004. Retrieved January 31, 2011.^ “Debian 默认安全”。 Debian：SbD。原始存档于 2004 年 11 月 3 日。2011 年 1 月 31 日检索。
^"Chapter 2. What's new in Debian 7.0". Release Notes for Debian 7.0 (wheezy), 32-bit PC. Debian. Archived from the original on June 6, 2014. Retrieved May 27, 2014.^ “第 2 章。Debian 7.0 中的新功能”。 Debian 7.0 (wheezy)，32 位 PC 发行说明。德比安。原始存档于 2014 年 6 月 6 日。2014 年 5 月 27 日检索。
^"CVE-2008-0166". MITRE. Archived from the original on July 14, 2014. Retrieved July 21, 2014.^ “CVE-2008-0166”。斜接。原始存档于 2014 年 7 月 14 日。2014 年 7 月 21 日检索。
^Amor, J. J.; Robles, G.; González-Barahona, J. M.; Rivas, F.: Measuring Lenny: the size of Debian 5.0Archived March 24, 2021, at the Wayback Machine ResearchGate^ Amor, J. J.；罗伯斯，G.； González-Barahona, J. M.； Rivas, F.: Measuring Lenny: the size of Debian 5.0 互联网档案馆的存档，存档日期 2021 年 3 月 24 日，网址为 Wayback Machine ResearchGate
^"Estimated Cost". Black Duck Open Hub. Archived from the original on August 8, 2014. Retrieved January 6, 2016.^ “估计费用”。黑鸭开放集线器。原始存档于 2014 年 8 月 8 日。2016 年 1 月 6 日检索。
^Larabel, Michael. "Devuan: Debian Without Systemd". Phoronix. Archived from the original on December 11, 2014. Retrieved December 14, 2014.^ 拉拉贝尔，迈克尔。 “Devuan：没有 Systemd 的 Debian”。凤凰。原始存档于 2014 年 12 月 11 日。2014 年 12 月 14 日检索。
People's Republic of China中华人民共和国 Loongson Industrial Park, Building 2, Zhongguancun Environmental protection park, Haidian District, Beijing, China中国北京市海淀区中关村环保园2号楼龙芯产业园
Area served服务区域
Global全球的
Key people关键人物
Chairman主席
Dr.Hu Wei Wu胡伟武博士
Services服务
Chip design, motherboard design, operating system and kernel maintenance, important software and library maintenance芯片设计、主板设计、操作系统及内核维护、重要软件及库维护
Loongson (simplified Chinese: 龙芯; traditional Chinese: 龍芯; pinyin: Lóngxīn; lit. 'Dragon Chip')[1] is the name of a family of general-purpose, MIPS architecture-compatible microprocessors, as well as the name of the Chinese fabless company (Loongson Technology) that develops them. The processors are alternately called Godson processors,[2] which are described as its academic name.[3]龙芯（简体中文：龙芯；繁体中文：龙芯；拼音：Lóngxīn；lit. 'Dragon Chip'）[1] 是通用、MIPS 架构兼容微处理器系列的名称，也是开发它们的中国无晶圆厂公司（龙芯科技）。这些处理器也被称为龙芯处理器，[2] 被描述为其学术名称。 [3]
The Godson processors, based on MIPS architecture, were initially developed at the Institute of Computing Technology (ICT), Chinese Academy of Sciences (CAS).[4] The chief architect was Professor Hu Weiwu [zh].[citation needed] The development of the first Loongson chip was started in 2001.[5][6] The aim of the Godson project was to develop "high performance general-purpose microprocessors in China",[2] and to become technologically self-sufficient as part of the Made in China 2025 plan.[5] The development was supported by funding via the 10th and 11thFive-Year Plans.[7][8]基于 MIPS 架构的龙芯处理器最初是由中国科学院计算技术研究所 (ICT) 开发的。 [4]首席架构师是胡伟武教授[zh]。[引证需要]第一款龙芯芯片的开发始于 2001 年。[5][6]龙芯项目的目标是“在中国开发高性能通用微处理器”，[2] 并作为中国制造 2025 计划的一部分在技术上实现自给自足。 [5]这一发展得到了第十个和第十一个五年计划的资金支持。 [7][8]
In 2010 the company was commercialised as a separate entity,[5] and in April 2010 Loongson Technology Corporation Limited was formally established and settled in Zhongguancun, Beijing, China.[citation needed] The company is a public–private partnership between ICT and Beijing-based chip designer BLX IC Design Corporation.[6]BLX itself was a spin-off from ICT, and was founded in 2002 with Jiangsu Zhongyi Group. As Loongson is a fabless designer, STMicroelectronics fabricates and markets the processors.[6][5]2010 年，公司作为独立实体商业化，[5] 2010 年 4 月，龙芯科技有限公司正式成立并落户中国北京中关村。[引文需要] 该公司是 ICT 与北京之间的公私合作伙伴关系基芯片设计公司 BLX IC Design Corporation.[6] BLX 本身是 ICT 的衍生公司，于 2002 年与江苏中意集团成立。由于龙芯是一家无晶圆厂设计商，意法半导体负责制造和销售处理器。 [6][5]
The South China Morning Post reported that since 2020, Loongson has partnered with UnionTech and Sunway to develop and promote the Debian Linux-based Deepin operating system to reduce Chinese computers dependency on Microsoft Windows.[9][10]《南华早报》报道称，自2020年以来，龙芯与联泰科技和神威合作开发和推广基于Debian Linux的Deepin操作系统，以减少中国计算机对微软Windows的依赖。[9][10]
In 2021, Loongson filed for an initial public offering on the Shanghai Stock Exchange STAR Market.[5][11] The company was seeking to raise US$500 million.[11] Details from this time suggested Loongson needing RMB 400,000,000 annual funding, for the first 10 years of its existence, and the company only broke even in 2015.[12]2021年，龙芯在上海证券交易所科创板申请首次公开发行股票。[5][11]该公司正在寻求筹集 5 亿美元。 [11]这段时间的细节表明，龙芯在成立的前 10 年每年需要 4 亿元人民币的资金，而公司在 2015 年才实现收支平衡。 [12]
Loongson began by using the MIPS64instruction set architecture (ISA). The internal microarchitecture was independently developed by ICT.[citation needed] Early implementations of the family lacked four instructions patented by MIPS Technologies (US4814976A, unaligned load-store) to avoid legal issues.[15][16]龙芯开始使用 MIPS64 指令集架构 (ISA)。内部微架构由 ICT 独立开发。[需要引用] 该系列的早期实现缺少 MIPS 技术公司获得专利的四个指令（US4814976A，未对齐的加载存储）以避免法律问题。[15][16]
In 2007, a deal was reached by MIPS Technologies and ICT. STMicroelectronics bought a MIPS license for Loongson, and thus the processor can be promoted as MIPS-based or MIPS-compatible instead of MIPS-like.[17][18][19]2007 年，MIPS 科技与 ICT 达成交易。 STMicroelectronics 为龙芯购买了 MIPS 许可证，因此处理器可以宣传为基于 MIPS 或 MIPS 兼容，而不是 MIPS-like。 [17][18][19]
In June 2009, ICT licensed the MIPS32 and MIPS64 architectures directly from MIPS Technologies.[20]2009 年 6 月，ICT 直接从 MIPS Technologies 获得了 MIPS32 和 MIPS64 架构的许可。 [20]
In August 2011, Loongson Technology Corp. Ltd. licensed the MIPS32 and MIPS64 architectures from MIPS Technologies, Inc. for continued development of MIPS-based Loongson CPU cores.[21][22]2011 年 8 月，龙芯科技有限公司从 MIPS Technologies, Inc. 获得 MIPS32 和 MIPS64 架构许可，用于继续开发基于 MIPS 的龙芯 CPU 内核。 [21][22]
The Loongson 3A2000 in 2015 saw the adoption of 2015年龙芯3A2000采用LoongISA龙ISA 1.0, an expanded instruction set that is a superset of MIPS64 release 2.[23][8] It can be broken down into:[24]1.0，一个扩展指令集，是 MIPS64 版本 2 的超集。[23][8]它可以分解为：[24]
The LoongISA instructions were introduced as part of the GS464E cores.[8] The binary translation instructions have the specific benefit of speeding up Intel x86 CPU emulation at a cost of 5% of the total die area. The new instructions help a QEMU hypervisor translate instructions from x86 to MIPS with only a reported 30% performance penalty.[25][26]LoongISA 指令作为 GS464E 内核的一部分引入。 [8]二进制翻译指令具有加速 Intel x86 CPU 仿真的特定优势，而成本仅为总管芯面积的 5%。新指令帮助 QEMU 虚拟机管理程序将指令从 x86 转换为 MIPS，据报道性能损失仅为 30%。 [25][26]
LoongISA 2.0 was introduced for the GS464V R2 core, with the release of the Loongson 3 4000 series. Compared to LoongISA 1.0, the DSP module is removed, and a few sets are added:[citation needed]随着龙芯3 4000系列的发布，GS464V R2核心引入了LoongISA 2.0。与LoongISA 1.0相比，去掉了DSP模块，增加了几组：[引文需要]
LoongSX龙盛祥
LoongASX龙澳证券交易所
LoongEXT3 (updated)LoongEXT3（更新）
LoongAMU龙妈
Loongson SIMD instructions are semi-classified and are unavailable in publicly available compilers and assemblers, Loongson 2F's LoongMMI being the sole exception. A similar status applies to other LoongISA extensions.
龙芯SIMD指令是半保密的，在公开可用的编译器和汇编器中不可用，龙芯2F的LoongMMI是唯一的例外。类似的状态适用于其他 LoongISA 扩展。
Loongson moved to their own processor instruction set architecture (ISA) in 2021 with the release of the Loongson 3 5000 series.[27][28][29] A Loongson developer described it as "...a new RISC ISA, which is a bit like MIPS or RISC-V. LoongArch includes a reduced 32-bit version (LA32R), a standard 32-bit version (LA32S) and a 64-bit version (LA64)".[30] The stated rationale was to make Loongson and China not dependent on foreign technology or authorisation to develop their processor capability, whilst not infringing on any technology patents.[31]随着龙芯 3 5000 系列的发布，龙芯在 2021 年转向了自己的处理器指令集架构 (ISA)。[27][28][29]一位龙芯开发人员将其描述为“……一个新的 RISC ISA，有点像 MIPS 或 RISC-V。LoongArch 包括一个简化的 32 位版本（LA32R）、一个标准的 32 位版本（LA32S）和一个 64 -位版本 (LA64)".[30]陈述的理由是让龙芯和中国不依赖外国技术或授权来开发他们的处理器能力，同时不侵犯任何技术专利。 [31]
The ISA has been referred to as "a fork of MIPS64r6" due to a perceived lack of changes judging from instruction listings.[32][33] In August 2021, Linux maintainers[who?] complained that submitted LoongArch code is "...a blind copy of the MIPS code...", however "only with a different name".[34]由于从指令列表判断缺乏变化，ISA 被称为“MIPS64r6 的一个分支”。 [32][33] 2021 年 8 月，Linux 维护者[谁？] 抱怨提交的 LoongArch 代码是“...MIPS 代码的盲目复制...”，但“只是名称不同”。[34]
The LoongArch ISA manual has been made partially available in August 2021 with the publication of its first volume documenting the basic architecture.[35] According to the LoongArch manual, the ISA uses MIPS's privilege model and IRQ mechanism, with other parts mostly following RISC-V's practice: the delay slot is removed and the instruction encoding is changed.[35] Similar to LoongISA, the instruction-set extensions (SIMD and binary translation) are not yet documented, making this functionality unusable.[35]LoongArch ISA 手册已于 2021 年 8 月部分可用，其第一卷记录了基本架构。[35]根据LoongArch手册，ISA使用了MIPS的特权模型和IRQ机制，其他部分大多沿袭了RISC-V的做法：去掉了延迟槽，改变了指令编码[35]。与 LoongISA 类似，指令集扩展（SIMD 和二进制翻译）尚未记录，使得此功能无法使用。 [35]
The Register reported in November 2021 that the suspicion that LoongArch combines the best parts of MIPS and RISC-V, along with custom instructions.[36] Commentary from Tom's Hardware re-states the issue that the Linux kernel code for LoongArch is the "same code it used for its MIPS-based chips"; they further note that Loongson "fails to demonstrate advantages of its architecture even on paper to software developers".[37]The Register 在 2021 年 11 月报道称，怀疑 LoongArch 结合了 MIPS 和 RISC-V 的最佳部分，以及自定义指令。 [36]来自 Tom's Hardware 的评论重申了 LoongArch 的 Linux 内核代码是“用于其基于 MIPS 的芯片的相同代码”的问题；他们进一步指出，龙芯“即使在纸面上也未能向软件开发人员展示其架构的优势”。[37]
The LoongArch microarchitecture is poorly documented, with the community speculating around a lot of the functions.[38] The community noted the similarities of LoongArch to MIPS and RISC-V, and that previous Linux kernel submissions were identical to MIPS code.[38]LoongArch 微架构的文档很少，社区猜测了很多功能。 [38]社区注意到 LoongArch 与 MIPS 和 RISC-V 的相似之处，并且之前提交的 Linux 内核与 MIPS 代码相同。 [38]
In February 2022 the developers had submitted patches to allow compilation to LoongArch within LLVM 15.0.[39]2022 年 2 月，开发人员提交了补丁，允许在 LLVM 15.0 中编译到 LoongArch。[39]
GS232 has a 5-stage pipeline at max. 500 MHz. L1 = 16KB.[citation needed] The GS 232 is mainly used for Godson-1 products.GS232 最多有 5 级流水线。 500 兆赫兹。 L1 = 16KB.[需要引用] GS 232 主要用于龙芯一号产品。
GS464 series: MIPS64 core with four-way superscalarout-of-order issue.[41] The design originated from the Loongson 2F processor.[8] It was first widely used in the Loongson 3A processor, before also being used in the Loongson 2 series.[41][42]GS464 系列：具有四路超标量乱序问题的 MIPS64 内核。 [41]该设计源于龙芯2F处理器。 [8]它首先被广泛应用于龙芯3A处理器，之后也被用于龙芯2系列。[41][42]
GS464 has support for MIPS64 R2 + LoongMMI (two different versions in 2E and 2F)[citation needed]GS464 支持 MIPS64 R2 + LoongMMI（2E 和 2F 中的两个不同版本）[需要引用]
GS464V was first introduced in 2010 with the Godson 3B, and is a GS464 with vector capabilities.[7][43]GS464V 于 2010 年随龙芯 3B 首次推出，是一款具有矢量功能的 GS464。 [7][43]
GS464E is an improved version of the GS464.[44] Development had started in 2012 after shortcomings were found in the GS464 processor.[8] The core has multiple improvements, including larger caches and better branch prediction amongst others, and was better optimised.[8] The core was extended to support LoongISA (in addition to the in addition to MIPS64 R2 architecture).[44]GS464E 是 GS464 的改进版本。 [44]在 GS464 处理器发现缺陷后，开发于 2012 年开始。 [8]核心有多项改进，包括更大的缓存和更好的分支预测等，并且得到了更好的优化。 [8]扩展内核以支持 LoongISA（除了 MIPS64 R2 架构之外）。 [44]
GS464EV is a development of the GS464 series, first used by the 3A4000 processor[45]GS464EV是GS464系列的发展，首先被3A4000处理器使用[45]
LA464 is the development of the GS464 to support LoongArch. Whilst the initial core of the 3A5000 was noted to be GS464, due to incompatible instruction sets Loongson renamed the 3A5000 core to LA464 in their documentation in August 2021.[38]LA464 是 GS464 的发展，支持 LoongArch。虽然 3A5000 的初始核心被认为是 GS464，但由于指令集不兼容，龙芯在 2021 年 8 月的文档中将 3A5000 核心更名为 LA464。 [38]
It has been noted by the community that the naming of the Loongson microarchitectures is not consistent, with different products being noted to have the same processor core, even though the instructions sets might not be exactly compatible.[38]社区注意到龙芯微架构的命名不一致，不同的产品被指出具有相同的处理器内核，即使指令集可能不完全兼容。 [38]
The first Loongson processor, the Godson-1, was designed in 2001, released in 2002, and is a 32-bit CPU running at a clock speed of 266 MHz.[6][3][26] It is fabricated with 0.18 micron CMOS process, has 8 KB of data cache, 8 KB of instruction cache and a 64-bit floating-point unit, capable of 200 double-precision MFLOPS.[46] Godson-1 series chips either use the GS132 or GS232 cores.[47]首款龙芯处理器龙芯一号于2001年设计，2002年发布，是一款主频为266MHz的32位CPU。[6][3][26]它采用 0.18 微米 CMOS 工艺制造，具有 8 KB 数据缓存、8 KB 指令缓存和一个 64 位浮点单元，能够达到 200 双精度 MFLOPS。[46]龙芯一号系列芯片使用 GS132 或 GS232 内核。 [47]
Loongson X is a radiation hardened version of the GS232 core used in the Godson-1.[8]龙芯 X 是龙芯一号中使用的 GS232 核心的抗辐射版本。 [8]
The Loongson 2 is a family of MIPS III compatible processors.[48][3] It adds 64-bit ability to the Loongson architecture.[6][26] Later Loongson 2 processors migrated to being MIPS64 compatible, due to sharing the GS464 core with the Loongson 3 series.[8] Whilst early 2 series processors were single core, they developed to become multicore.
龙芯 2 是 MIPS III 兼容处理器系列。 [48][3]它为龙芯架构增加了 64 位能力。 [6][26]由于与龙芯 3 系列共享 GS464 内核，后来的龙芯 2 处理器迁移到 MIPS64 兼容。 [8]虽然早期的 2 系列处理器是单核，但它们发展成为多核。
The development plan for the Godson-2 was to develop it from a CPU to a SOC.[3][7] The 2E (2006) was a CPU, the 2F (2007) integrated the north bridge, the 2G (2008) had a hyper transport link between the CPU/north bridge and an integrated GPU/south bridge, and the 2H (2009) integrated all these functions into a SOC.[3][7] The design of the 2F was the basis of the GS464 core.[8] The 2G uses a single GS464 core;[7] the 2H uses the GS464V core, as a single-core version of the initial Godson 3B.[43]龙芯二号的开发计划是将其从 CPU 开发成 SOC。 [3][7] 2E（2006）是一个CPU，2F（2007）集成了北桥，2G（2008）在CPU/北桥和集成GPU/南桥之间有一个超传输链路，2H（2009）集成了所有这些功能都集成到一个 SOC 中。[3][7] 2F 的设计是 GS464 核心的基础。 [8] 2G采用单核GS464；[7] 2H采用GS464V核，作为初代龙芯3B的单核版本[43]
The Loongson 3 family of processors are "...multi-core CPU[s] designed for high performance desktops, servers and clusters".[49][26] They were designed as the first Loongson processors that had multiple cores.[41] The processors were designed to use LoongISA - i.e. the MIPS64 ISA with additional extensions.[41] The designers also attempted to optimise x86 translation on the chip.[3]龙芯 3 系列处理器是“……专为高性能台式机、服务器和集群设计的多核 CPU”。[49][26]它们被设计为第一款具有多核的龙芯处理器。 [41]这些处理器被设计为使用 LoongISA——即具有额外扩展的 MIPS64 ISA。 [41]设计人员还尝试优化芯片上的 x86 转换。 [3]
The first production processor was the Loongson 3A, which used 4 GS464 cores.[41][25] The 65 nm Loongson 3A1000 is able to run at a clock speed near 1 GHz, with 4 CPU cores (~15 W) first and 8 cores later (40 W).[citation needed] In April 2010, Loongson 3A1000 was released with DDR2/3 DRAM support.[citation needed]第一个量产处理器是龙芯 3A，它使用 4 个 GS464 内核。[41][25] 65 nm 龙芯 3A1000 能够以接近 1 GHz 的时钟速度运行，首先是 4 个 CPU 内核（~15 W），然后是 8 个内核（40 W）。[需要引用] 2010 年 4 月，龙芯 3A1000 与 DDR2 一起发布/3 DRAM 支持。[需要引用]
The designers noted that they would produce a 3B chip with enhanced processing and vector capabilities, with 8 cores, and a 3C for server applications with up to 16 cores.[7][26] The 8-core Loongson 3B was noted to use the upgraded GS464V core, with extended vector capabilities.[43] This was followed by the Loonson 3C which used 16 GS464V cores.[43]设计人员指出，他们将生产具有增强处理和矢量功能的 8 核 3B 芯片，以及用于服务器应用的多达 16 核的 3C。 [7][26] 8 核龙芯 3B 被注意到使用升级的 GS464V 内核，具有扩展的矢量功能。 [43]其次是使用 16 个 GS464V 内核的 Loonson 3C。 [43]
The 3B1000, and related 2I, both failed as processors due to design errors.[23] In May 2013 development of the 3C was suspended, in favour of developing the 3A2000 processor.[23]由于设计错误，3B1000 和相关的 2I 作为处理器都失败了。 [23] 2013 年 5 月，3C 的开发被暂停，转而开发 3A2000 处理器。 [23]
In 2015, the 3A1500 and 3B2000 were released using the enhanced GS464E cores.[8] The improved microarchitecture core allowed better performance, reportedly 3 times as fast as the 3A1000, as well as introducing the LoongISA enhanced instruction set.[8] The 3A1500 was for embedded applications, whilst the 3B2000 was for servers and PCs.[8]2015 年，发布了使用增强型 GS464E 内核的 3A1500 和 3B2000。 [8]改进后的微架构内核实现了更好的性能，据报道速度是 3A1000 的 3 倍，并且还引入了 LoongISA 增强型指令集。 [8] 3A1500 用于嵌入式应用，而 3B2000 用于服务器和 PC。 [8]
In 2017 Loongson released the 3A3000. The 3A3000 is designed with quad-core 64-bit and clocked at 1.5 GHz, power consumption is only 30 W.[citation needed] The performance of the 3A3000 is reported to be equivalent to the Intel J1900 processor (released in 2013).[45]2017年龙芯发布3A3000。 3A3000 采用四核 64 位设计，主频为 1.5 GHz，功耗仅为 30 W。[需要引用]据报道，3A3000 的性能相当于英特尔 J1900 处理器（2013 年发布）。[ 45]
In late-2019 the 3A and 3B 4000 series were released. They used the upgraded GS464EV microarchitecture.[45] The processors are designed with four cores, 8MB of L3 cache and operating clocks between 1.8 GHz to 2 GHz.[citation needed]2019 年底发布了 3A 和 3B 4000 系列。他们使用了升级后的 GS464EV 微架构。 [45]这些处理器设计有四个内核、8MB 的 L3 缓存和 1.8 GHz 至 2 GHz 之间的工作时钟。[需要引用]
In July 2021 the Loongson 3 5000 series was released.[29] The processor series is Loongson's first with their own developed ISA, "LoongArch".[29] The processors announced include the 3A5000, a four-core desktop CPU, and the 3C5000L, a sixteen-core server CPU based on four 3A5000 in a single package.[32][28][36] Both CPUs are reported to be fabricated on a 12 nm process. Whilst the processor was noted to be using the GS464V cores initially, due to incompatibility with previous versions, the cores were renamed to LA464 in August 2021.[38]2021年7月发布龙芯3 5000系列[29]该系列处理器是龙芯首款自主研发的ISA“LoongArch”[29]。宣布的处理器包括 3A5000，一个四核台式机 CPU 和 3C5000L，一个十六核服务器 CPU，基于单个封装中的四个 3A5000。[32][28][36]据报道，这两款 CPU 均采用 12 纳米工艺制造。虽然注意到该处理器最初使用的是 GS464V 内核，但由于与以前的版本不兼容，该内核于 2021 年 8 月更名为 LA464。 [38]
The Register reported that "the 3A5000 is said to be 50 per cent faster and 30 per cent more power efficient" than the preceding 3A4000.[36]Phoronix reports that the 3A5000 CPU is "roughly on a par with the likes of the Intel Core i3 8109U / Core 2 Quad Q9500 / Core i5 750, or Armv8-based Phytium FT-2000".[29][27]据 The Register 报道，“据说 3A5000 比之前的 3A4000 快 50%，能效高 30%”。 [36] Phoronix 报告称，3A5000 CPU“与英特尔酷睿 i3 8109U / 酷睿 2 四核 Q9500 / 酷睿 i5 750 或基于 Armv8 的飞腾 FT-2000 等处理器大致相当”。[29][27]
In 2022 Loongson announced their 6000 series processors.[50] The updated processor architecture will use "LA664" cores.,[50] and the company noted that the single-core performance will rival that of AMD's Zen 3 and Intel's Tiger Lake architecture.[50]2022 年，龙芯发布了他们的 6000 系列处理器。 [50]更新后的处理器架构将使用“LA664”内核。,[50] 该公司指出，单核性能将与 AMD 的 Zen 3 和英特尔的 Tiger Lake 架构相媲美。[50]
The Loongson processors are mainly designed around using the Linux operating system.[51] Any operating system supporting the MIPS architecture should theoretically work. Windows CE was ported to a Loongson-based system with minimal effort.[52] In 2010, Lemote ported an Android distribution to the Loongson platform.[53]龙芯处理器主要围绕使用 Linux 操作系统而设计。 [51]任何支持 MIPS 架构的操作系统在理论上都应该可以工作。 Windows CE 以最小的努力移植到基于龙芯的系统。 [52] 2010年，Lemote将Android发行版移植到龙芯平台[53]。
Loongson machines are used in the package-building and CI infrastructure of Debian and Golang, respectively. This is partially because of Loongson's status as the only vendor producing application-grade MIPS CPUs for retail.[54][55]龙芯机器分别用于Debian和Golang的包构建和CI基础设施。这部分是因为龙芯是唯一一家生产零售应用级 MIPS CPU 的供应商。[54][55]
As of February 2022, there are 3 Chinese Linux distributions that support LoongArch: these are Kylin, Loongnix and Unity Operating System. There are efforts to build LoongArch support into community versions of Linux.[38]截至 2022 年 2 月，支持 LoongArch 的中文 Linux 发行版有 3 个：麒麟、Loongnix 和 Unity 操作系统。人们正在努力将 LoongArch 支持构建到 Linux 的社区版本中。 [38]
The GNU Compiler Collection (GCC) is the main compiler for software development on the Loongson platform.[56][57]GNU编译器集合（GCC）是龙芯平台软件开发的主要编译器。[56][57]
Before 2021 LLVM support was still inadequate due to missing workarounds for Loongson's CPU errata on MIPS.[58][38]在 2021 年之前，由于龙芯在 MIPS 上的 CPU 勘误缺少解决方法，LLVM 支持仍然不足。[58][38]
ICT also ported Open64 to the Loongson II platform.[59]ICT也将Open64移植到龙芯二代平台上。 [59]
LoongArch is supported by the GCC, LLVM, Golang compilers, and supports the Java, JavaScript and .NETvirtual machines.[60]LoongArch 受 GCC、LLVM、Golang 编译器支持，并支持 Java、JavaScript 和 .NET 虚拟机。 [60]
Lemote FuLoong and YeeLoong with a Loongson 2F microprocessor带龙芯 2F 微处理器的 Lemote FuLoong 和 YeeLoong
Lemote's Fulong MiniPC on top of a CD-ROM drive as referenceLemote的Fulong MiniPC在CD-ROM驱动器之上作为参考
In 2012 it was reported that Loongson processors had found itself into very few computing systems.[6] The processors are mainly used in Chinese computers; in 2021 it was reported that Loongson supplies CPUs for most desktop computers procured by the Chinese government, and 80% of the Chinese government's servers.[12] The release of the 3A3000 processor in 2015 was noted as turning point for the company's fortunes.[12] In 2017 it was noted that the company's processors were being used in the Beidou satellite.[12][8]2012 年，有报道称龙芯处理器已进入极少数计算系统。 [6]处理器主要用于中国计算机；据报道，2021年龙芯为中国政府采购的大部分台式机和80%的中国政府服务器供应CPU。 [12] 2015 年 3A3000 处理器的发布被认为是公司命运的转折点。 [12] 2017 年，该公司的处理器被用于北斗卫星。[12][8]
In March 2006, a €100 Loongson II computer design called Longmeng (Dragon Dream) was announced by Lemote.[citation needed]2006 年 3 月，Lemote 宣布了一款名为 Longmeng（龙之梦）的 100 欧元龙芯 II 计算机设计。[需要引用]
In June 2006 at Computex'2006, YellowSheepRiver announced the Municator YSR-639,[81] a small form factor computer based on the 400 MHz Loongson 2.
2006 年 6 月，在 Computex'2006 上，YellowSheepRiver 发布了 Municator YSR-639，[81] 一款基于 400 MHz 龙芯 2 的小型计算机。
As of November 2008 the new 8.9" netbook from the Chinese manufacturer Lemote that replaced mengloong, Yeeloong (Portable Dragon),[82] running Debian, is available[83] in Europe from the Dutch company Tekmote Electronics.
截至 2008 年 11 月，来自中国制造商 Lemote 的新型 8.9" 上网本取代了 mengloong，Yeeloong（便携龙），[82] 运行 Debian，[83] 在欧洲由荷兰公司 Tekmote Electronics 提供。
In January 2010, Jiangsu province planned to buy 1.5 million Loongson PCs.[84]2010年1月，江苏省计划采购150万台龙芯PC[84]。
In September 2011, Lemote announced the Yeeloong-8133 13.3" laptop featuring 900 MHz, quad-core Loongson-3A/2GQ CPU.[85]2011 年 9 月，Lemote 发布了 Yeeloong-8133 13.3" 笔记本电脑，配备 900 MHz 四核龙芯 3A/2GQ CPU。[85]
On 26 December 2007, China revealed its first Loongson based supercomputer in Hefei. The KD-50-I has a reported peak performance of 1 TFLOPS, and about 350 GFLOPS measured by LINPACK.[86] This supercomputer was designed by a joint team led by Chen Guoliang at the computer science technology department of the University of Science and Technology of China (USCT) and ICT (the secondary contractor). KD-50-I is the first Chinese built supercomputer to utilize domestic Chinese CPUs, with a total of more than 336 Loongson-2F CPUs, and nodes interconnected by ethernet. The size of the computer was roughly equivalent to a household refrigerator and the cost was less than RMB800,000 (approximately US$120,000, €80,000).[87]2007年12月26日，中国第一台基于龙芯的超级计算机在合肥亮相。据报道，KD-50-I 的峰值性能为 1 TFLOPS，LINPACK 测得约为 350 GFLOPS。 [86]这台超级计算机是由中国科学技术大学（USCT）计算机科学技术系陈国良领导的联合团队和ICT（二次承包商）设计的。 KD-50-I是中国制造的第一台使用国产CPU的超级计算机，共有超过336个龙芯2F CPU，节点通过以太网互连。这台电脑的大小大约相当于一台家用冰箱，成本不到 80 万元人民币（约合 12 万美元、8 万欧元）。 [87]
On 20 April 2010, USTC announced the successful development of the Loongson 3A based KD-60-1. The supercomputer is a cluster of standard blade servers with a total of over 80 quad-core Loongson processors, providing theoretical peak performance of 1 TFLOPS and reduces power consumption by 56% compared to the KD-50-I system, with similar performance.[88]2010年4月20日，中国科大宣布基于龙芯3A的KD-60-1研制成功。该超级计算机为标准刀片服务器集群，共有80多颗四核龙芯处理器，理论峰值性能可达1 TFLOPS，与KD-50-I系统相比功耗降低56%，性能相近。 88]
On 26 December 2012, USTC announced the Loongson 3B based KD-90-1. Based around blade servers, like the KD-60-1, the supercomputer has over 10 octo-core Loongson processors, providing theoretical peak performance of 1 TFLOPS, and reduces power consumption by 62% compared to the KD-60 system that has similar performance.[89]2012年12月26日，中国科学技术大学宣布基于龙芯三号乙的KD-90-1。超级计算机以刀片服务器为基础，如KD-60-1，拥有超过10个八核龙芯处理器，提供1 TFLOPS的理论峰值性能，与具有类似性能的KD-60系统相比，功耗降低了62% .[89]
In 2012 it was reported that Loongson processors were to be found in the Sunway BlueLight MPP and Dawning 6000 supercomputers.[6]2012年，有报道称双威蓝光MPP和曙光6000超级计算机将采用龙芯处理器。 [6]
^The Godson/Loongson 2 series processors have been developed and named mostly sequentially in an alphabetical format.^ 龙芯/龙芯 2 系列处理器的开发和命名大多按字母顺序排列。
^The Godson/Loongson 3 series processors seem to be named according to segment and then a generation number. The segment tends to be A (general purpose PCs), B (seemingly high core counts) and C (server processors). The generation numbers start at 1000 for the first series processors, and then increment generally to the next thousand. There are some processors that may be between generation products, that have a x5000 designation.^ 龙芯/龙芯 3 系列处理器似乎是按段命名的，然后是代号。该细分市场往往是 A（通用 PC）、B（看似高核心数）和 C（服务器处理器）。第一个系列处理器的世代编号从 1000 开始，然后通常递增到下一千。某些处理器可能介于两代产品之间，具有 x5000 名称。
^ Jump up to: abHu, Weiwu; Wang, Jian; Gao, Xiang; Chen, Yunji; Liu, Qi; Li, Guojie (March 2009). "Godson-3: A Scalable Multicore RISC Processor with x86 Emulation". IEEE Micro. 29 (2): 17–29. doi:10.1109/MM.2009.30. S2CID726798. Retrieved 29 July 2021.^ Jump up to: a b Hu, Weiwu; Wang, Jian; Gao, Xiang; Chen, Yunji; Liu, Qi; Li, Guojie (March 2009). "Godson-3: A Scalable Multicore RISC Processor with x86 Emulation". IEEE Micro. 29 (2): 17–29. doi:10.1109/MM.2009.30. S2CID 726798. Retrieved 29 July 2021.
^ Jump up to: abcdefgMorgan, Timothy Prickett (25 February 2011). "Godson: China shuns US silicon with faux x86 superchip". www.theregister.com. Retrieved 4 August 2021.^ Jump up to: a b c d e f g Morgan, Timothy Prickett (25 February 2011). "Godson: China shuns US silicon with faux x86 superchip". www.theregister.com. Retrieved 4 August 2021.
^ Jump up to: abApril 2021, Anton Shilov 16 (16 April 2021). "Loongson Technology Develops Its Own CPU Instruction Set Architecture". Tom's Hardware. Retrieved 28 July 2021.^ Jump up to: a b April 2021, Anton Shilov 16 (16 April 2021). "Loongson Technology Develops Its Own CPU Instruction Set Architecture". Tom's Hardware. Retrieved 28 July 2021.
^ Jump up to: abcdShah, Agam (2 November 2021). "Loongson chip is China's next step to semiconductor freedom". www.theregister.com. Retrieved 1 December 2021.^ Jump up to: a b c d Shah, Agam (2 November 2021). "Loongson chip is China's next step to semiconductor freedom". www.theregister.com. Retrieved 1 December 2021.
^Shilov, Anton (25 August 2021). "Loongson Rips MIPS: Uses Old Code for New CPUs". Tom's Hardware. Retrieved 1 December 2021.^ Shilov, Anton (25 August 2021). "Loongson Rips MIPS: Uses Old Code for New CPUs". Tom's Hardware. Retrieved 1 December 2021.
^Larabel, Michael (10 February 2022). "LoongArch CPU Support Begins Landing In LLVM". www.phoronix.com. Retrieved 29 March 2022.^ 迈克尔·拉拉贝尔（2022 年 2 月 10 日）。 “LoongArch CPU 支持开始登陆 LLVM”。 www.phoronix.com。 2022 年 3 月 29 日检索。
^ Jump up to: abc"你不曾见过的国产CPU：可能是最全的龙芯系列芯片家谱（下）". www.ijiwei.com (in Chinese). 1 June 2019. Retrieved 12 August 2021.^ 跳转至： a b c 《最重要的CPU之一：拥有流畅的存储设备很重要（一）》。 www.ijiwei.com（中文）。 2019 年 6 月 1 日。8 月 12 日检索
^HU Wei-Wu (2003). TANG Zhi-Min. "Architecture of the Godson-1 Processor". Chinese Journal of Computers (4).^ HU Wei-Wu (2003). TANG Zhi-Min. "Architecture of the Godson-1 Processor". Chinese Journal of Computers (4).
^"成功研制以龙芯为内核的税控SOC芯片 苏州中科集成电路设计中心". szicc.com.cn. Retrieved 8 May 2019.^ "成功研制以龙芯为内核的税控SOC芯片 苏州中科集成电路设计中心". szicc.com.cn. Retrieved 8 May 2019.
^"龙芯1A_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.^ "龙芯1A_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.
^"龙芯1B_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.^ "龙芯1B_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.
^"龙芯1C_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.^ "龙芯1C_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.
^"龙芯1C101_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.^ "龙芯1C101_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.
^"龙芯1D_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.^ "龙芯1D_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.
^"龙芯2F_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.^ "龙芯2F_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.
^"龙芯2G用户手册"(PDF). Archived from the original(PDF) on 29 November 2020. Retrieved 19 August 2019.^ "龙芯2G用户手册" (PDF). Archived from the original (PDF) on 29 November 2020. Retrieved 19 August 2019.
^"龙芯2K1000_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.^ "龙芯2K1000_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.
^"龙芯3A1000_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.^ "龙芯3A1000_龙芯官方网站-[龙芯官方网站]". loongson.cn. Archived from the original on 8 May 2019. Retrieved 8 May 2019.
^"龙芯3B1500_龙芯官方网站-[龙芯官方网站]". www.loongson.cn. Archived from the original on 30 January 2020. Retrieved 19 August 2019.^ "龙芯3B1500_龙芯官方网站-[龙芯官方网站]". www.loongson.cn. Archived from the original on 30 January 2020. Retrieved 19 August 2019.
^"龙芯3A3000/3B3000_龙芯官方网站-[龙芯官方网站]". www.loongson.cn. Archived from the original on 30 November 2016. Retrieved 19 August 2019.^ "龙芯3A3000/3B3000_龙芯官方网站-[龙芯官方网站]". www.loongson.cn. Archived from the original on 30 November 2016. Retrieved 19 August 2019.
^"Yeelong Specs". Archived from the original on 23 October 2008. (LinuxDevices, 22 Octobjer 2008)^ "Yeelong Specs". Archived from the original on 23 October 2008. (LinuxDevices, 22 Octobjer 2008)
^"我首台基于"龙芯3B"国产万亿次高性能计算机研制成功". www.360doc.com. Archived from the original on 29 November 2014. Retrieved 15 November 2014.^ "我首台基于"龙芯3B"国产万亿次高性能计算机研发成功"。 www.360doc.com。原始存档于 2014 年 11 月 29 日。2014 年 11 月 15 日检索。
Jiangsu Lemote Tech Co., Ltd or Lemote (Chinese: 航天龙梦; pinyin: hang tian lóng mèng; lit. 'Aerospace Dragon Dream') is a computer company established as a joint venture between the Jiangsu Menglan Group and the Chinese Institute of Computing Technology,[2] involved in computer hardware and softwareproducts, services, and projects.
江苏乐摩特科技有限公司或乐摩特（中文：航天龙梦；拼音：hang tian lóng mèng；lit. 'Aerospace Dragon Dream'）是江苏梦兰集团与中国计算机科学研究院合资成立的计算机公司。计算技术，[2] 涉及计算机硬件和软件产品、服务和项目。
In June 2006, shortly after Institute of Computing Technology of the Chinese Academy of Sciences developed Loongson 2E they need a company to build end product, so the Jiangsu Menglan Group began a joint venture with the Institute of Computing Technology of the Chinese Academy of Sciences. The venture was named Jiangsu Lemote Tech Co., Ltd.
2006年6月，在中科院计算所研发出龙芯2E后不久，他们需要一家公司来打造终端产品，于是江苏梦兰集团开始与中科院计算所合资。合资公司命名为江苏乐默特科技有限公司。
A computer was announced by Fuxin Zhang, an ICT researcher also a Lemote staff, who said the purpose of this project was to "provide everyone with a personal computer".[3] The device is intended for low income groups and rural area students.
一台计算机是由 ICT 研究员张福新宣布的，他也是 Lemote 的工作人员，他说这个项目的目的是“为每个人提供一台个人电脑”。 [3]该设备适用于低收入群体和农村地区的学生。
The Yeeloong netbook computer is intended to be built on free software[4] from the BIOS upwards, and for this reason is used and recommended by the founder of Free Software Foundation, Richard Stallman as of September 2008[5] and 23 January 2010.[6][7]Yeeloong 上网本计算机旨在从 BIOS 向上构建在免费软件[4] 上，因此，自由软件基金会的创始人 Richard Stallman 于 2008 年 9 月 [5] 和 2010 年 1 月 23 日使用和推荐。 [6][7]
Loongson insiders[8] revealed a new model based on the Loongson 3A quad-core laptop has been developed and was expected to launch in August 2011. With a similar design to the MacBook Pro[9] from Apple Inc., it will carry a Linux operating system by default.[10]龙芯内部人士[8]透露，一款基于龙芯3A四核笔记本电脑的新机型已经开发完成，预计将于2011年8月推出。其设计与苹果公司的MacBook Pro[9]相似，搭载默认为 Linux 操作系统。 [10]
In September 2011, Lemote announced the Yeeloong-8133 13.3" laptop featuring 900 MHz, quad-core Loongson-3A/2GQ CPU.[11]2011 年 9 月，Lemote 发布了 Yeeloong-8133 13.3" 笔记本电脑，配备 900 MHz 四核 Loongson-3A/2GQ CPU。 [11]
Fuloong 2 series of small desktop computers[edit]福龙2系列小型台式电脑[编辑]
The Fuloong 2 series is a desktop computer that costs CN¥1,015, €100, US$131.[citation needed] It ships with two Linux distributions, Debian and Rays Linux, but any other distribution that has a mipsel port can be installed, e.g. Gentoo Linux.
The Fuloong 2 series is a desktop computer that costs CN¥1,015, €100, US$131.[citation needed] It ships with two Linux distributions, Debian and Rays Linux, but any other distribution that has a mipsel port can be installed, e.g. Gentoo Linux.
The Fuloong 2F computer[12] was released on 30 June 2008, priced at CN¥1,800, about €163, $257.
Fuloong 2F 电脑[12] 于 2008 年 6 月 30 日发布，售价 1,800 元人民币，约合 163 欧元，257 美元。
Power supply: external 12 V power adapter电源：外置12V电源适配器
Operating system: Xinhua Hualay Rays 2.0, which is a Linux distribution that supports MIPS architecture. Fuloong 2F also works well with other Linux distributions,[12] OpenBSD,[13] and NetBSD.[14]操作系统：Xinhua Hualay Rays 2.0，是一个支持MIPS架构的Linux发行版。 Fuloong 2F 也适用于其他 Linux 发行版，[12] OpenBSD，[13] 和 NetBSD。 [14]
Lemote has participated in development and MIPS-porting of DebianGNU/Linux, eCos, MicroC/OS-II, VxWorks, Microsoft Windows CE, Java, OpenOffice.org and Yongzhong Office by Wuxi Yongzhong Tech Co. It also develops a Loongson processorsimulator based on GXemul. In part to its ability to run only libre software, without proprietary binary blobs, Richard Stallman famously used the Lemote Yeeloong.[16]Lemote参与了无锡永众科技有限公司Debian GNU/Linux、eCos、MicroC/OS-II、VxWorks、Microsoft Windows CE、Java、OpenOffice.org和Yongzhong Office的开发和MIPS移植，并开发了龙芯处理器模拟器基于 GXemul。理查德·斯托曼 (Richard Stallman) 以其著名的 Lemote Yeeloong [16] 的使用而闻名，部分原因在于其仅运行自由软件而无需专有二进制 blob 的能力。
^Masłowski, Michał Tomasz (3 September 2012). "Lemote YeeLoong 8101B with Loongson 2F CPU review". Retrieved 22 May 2014.^ Masłowski, Michał Tomasz（2012 年 9 月 3 日）。 “带龙芯 2F CPU 的 Lemote YeeLoong 8101B 评测”。 2014 年 5 月 22 日检索。
^"What do people use to get stuff done?". The Setup (An Interview with Richard Stallman). Uses this. 23 January 2010. Archived from the original on 17 July 2011. Retrieved 24 January 2010.^ “人们用什么来完成工作？”。设置（Richard Stallman 访谈）。用这个。 2010 年 1 月 23 日。原始存档于 2011 年 7 月 17 日。2010 年 1 月 24 日检索。
^Stallman, Richard (2012). "How I do my computing". Retrieved 22 May 2014.^ 斯托曼，理查德 (2012)。 “我如何进行计算”。 2014 年 5 月 22 日检索。
^ Jump up to: ab"Fuloong Mini-PC". Lemote. Jiangsu Lemote Tech Co. Archived from the original on 11 May 2010. Retrieved 28 October 2011.^ 跳转至： a b "Fuloong Mini-PC".乐莫特。 Jiangsu Lemote Tech Co. 原件存档于 2010 年 5 月 11 日。2011 年 10 月 28 日检索。
^"OpenBSD-Loongson". OpenBSD. 21 May 2011. Archived from the original on 15 June 2010. Retrieved 28 October 2011.^ “OpenBSD-龙芯”。打开BSD。 2011 年 5 月 21 日。原始存档于 2010 年 6 月 15 日。2011 年 10 月 28 日检索。
Portage is a package management system originally created for and used by Gentoo Linux and also by ChromeOS, Calculate, Sabayon, and Funtoo Linux among others. Portage is based on the concept of ports collections. Gentoo is sometimes referred to as a meta-distribution due to the extreme flexibility of Portage, which makes it operating-system-independent.[2][3][4][5] The Gentoo/Alt project was concerned with using Portage to manage other operating systems, such as BSDs, macOS and Solaris. The most notable of these implementations is the Gentoo/FreeBSD project.
Portage 是一个包管理系统，最初是为 Gentoo Linux 以及 ChromeOS、Calculate、Sabayon 和 Funtoo Linux 等创建并使用的。 Portage 基于端口集合的概念。由于 Portage 的极大灵活性，Gentoo 有时被称为元发行版，这使其独立于操作系统。[2][3][4][5] Gentoo/Alt 项目关注使用 Portage 来管理其他操作系统，例如 BSD、macOS 和 Solaris。这些实现中最著名的是 Gentoo/FreeBSD 项目。
There is an ongoing effort called the Package Manager Specification project (PMS),[6] which aims to standardise and document the behaviour of Portage, allowing the ebuild tree and Gentoo system packages to be used with alternative package managers such as Paludis and pkgcore. Its goal is to specify the exact set of features and behaviour of package managers and ebuilds, serving as an authoritative reference for Portage.
有一项名为包管理器规范项目 (PMS) 的持续工作，[6] 旨在标准化和记录 Portage 的行为，允许 ebuild 树和 Gentoo 系统包与替代包管理器（如 Paludis 和 pkgcore）一起使用。它的目标是指定包管理器和 ebuild 的确切功能和行为集，作为 Portage 的权威参考。
Portage is similar to the BSD-style package management known as ports, and was originally designed with FreeBSD's ports in mind.[7] Portage is written in the Python programming language, and is the main utility that defines Gentoo. Although the system itself is known as Portage, it consists of two main parts, the ebuild system and emerge. The ebuild system takes care of the actual work of building and installing packages, while emerge provides an interface to ebuild: managing an ebuild repository, resolving dependencies and similar issues. (These two therefore have roughly the same relation as rpm has with yum, or dpkg has with APT.)
Portage 类似于称为 ports 的 BSD 风格的包管理，最初是为 FreeBSD 的 ports 设计的。 [7] Portage 是用 Python 编程语言编写的，是定义 Gentoo 的主要实用程序。虽然系统本身被称为 Portage，但它由两个主要部分组成，即 ebuild 系统和 emerge。 ebuild 系统负责构建和安装包的实际工作，而 emerge 提供 ebuild 的接口：管理 ebuild 存储库、解决依赖关系和类似问题。 （因此，这两者的关系大致与 rpm 与 yum 的关系，或 dpkg 与 APT 的关系相同。）
A GTK+-based GUI, Porthole, is available for working with Portage.
There is also the Himerge GUI, which stands for "Haskell Interface for eMerge".
基于 GTK+ 的 GUI，Porthole，可用于与 Portage 一起工作。还有 Himerge GUI，代表“Haskell Interface for eMerge”。
Portage is characterized by its main function: compiling from source code the packages the user wishes to install. In doing so it allows customization of compiler and target-application options to fit the system's specifications and the user's own wishes. Functionalities related to system management include: allowing parallel package-version installation, tracking cross-package dependencies, managing a database of installed packages, providing a local ebuild repository, and synchronizing of the local Portage tree with remote repositories. Functionalities related to individual package installation include: specifying compilation settings for the target machine and choosing package components.
Portage 的主要功能是：从源代码编译用户希望安装的包。在这样做时，它允许定制编译器和目标应用程序选项，以适应系统规范和用户自己的愿望。与系统管理相关的功能包括：允许并行包版本安装、跟踪跨包依赖性、管理已安装包的数据库、提供本地 ebuild 存储库以及本地 Portage 树与远程存储库的同步。与单个包安装相关的功能包括：指定目标机器的编译设置和选择包组件。
Portage distinguishes between three levels of stability in ebuilds: stable (e.g., the software works as intended with no known security issues at time of release), keyword masked (mainly for packages that have not been sufficiently tested on the target system architecture to be considered stable) and hard masked (broken or very insecure) packages.
Portage 区分了 ebuild 中的三个稳定性级别：稳定（例如，软件按预期工作，在发布时没有已知的安全问题）、关键字屏蔽（主要针对尚未在目标系统架构上进行充分测试的软件包）稳定）和硬屏蔽（损坏或非常不安全）的包。
The emerge command-line tool is the heart of Portage. The command is customizable with many options and modifiers. The emerge tool is the most important utility for accessing the features of Portage from the command line.
emerge 命令行工具是 Portage 的核心。该命令可以使用许多选项和修饰符进行自定义。 emerge 工具是从命令行访问 Portage 功能的最重要的实用程序。
The program calculates and manages dependencies, executes ebuilds and maintains the local Portage tree and database of installed packages. The compilation settings used by ebuilds can be changed through the CFLAGSenvironment variable, based on the specifications of the individual computer and on the user's desire for optimization. The emerge utility executes ebuilds in a sandbox environment. This way the system is protected from software executed by the ebuild and resulting binaries are only merged after a successful build and sandboxed install.
该程序计算和管理依赖关系，执行 ebuilds 并维护本地 Portage 树和已安装软件包的数据库。 ebuilds 使用的编译设置可以通过 CFLAGS 环境变量进行更改，这取决于个人计算机的规格和用户对优化的期望。 emerge 实用程序在沙盒环境中执行 ebuild。通过这种方式，系统可以免受 ebuild 执行的软件的影响，并且生成的二进制文件仅在成功构建和沙盒安装后才会合并。
What emerge installs as dependencies is affected by the USE flag-settings. They decide which optional features will be included when installing or upgrading an application. The emerge command can also be used to download and install precompiled binary files.
emerge 作为依赖项安装的内容受 USE 标志设置的影响。他们决定在安装或升级应用程序时将包括哪些可选功能。 emerge 命令也可用于下载和安装预编译的二进制文件。
The Portage system offers the use of "USE flags", which allows users to indicate which software features they would like to include (and exclude) while building packages. For example, there is a USE flag to include DVD support, where available, in packages compiled with the flag enabled. The USE flags affect which dependencies are required, generally affecting which optional features will be built into a given program when it is compiled. For example, in packages which use a configure script, the USE flag feature would translate to ./configure --with-feature.
Portage 系统提供了“USE flags”的使用，它允许用户在构建包时指明他们想要包含（和排除）哪些软件功能。例如，有一个 USE 标志用于在启用该标志编译的包中包含 DVD 支持（如果可用）。 USE 标志会影响需要哪些依赖项，通常会影响编译时将哪些可选功能内置到给定程序中。例如，在使用配置脚本的包中，USE 标志功能将转换为 ./configure --with-feature。
The specification of USE flags is the usual way to configure programs on Gentoo. USE flags may be set manually, or via user-friendly tools such as 'ufed' (USE flag editor), which lists flags along with their description. A list of available USE flags is available at the Gentoo website's USE Flag Index.
USE 标志的规范是在 Gentoo 上配置程序的常用方法。 USE 标志可以手动设置，或通过用户友好的工具设置，例如“ufed”（USE 标志编辑器），它列出了标志及其描述。 Gentoo 网站的 USE Flag Index 提供了可用的 USE 标志列表。
Gentoo does not, by default, use binary packages as other package management systems do (like pacman or apt), employing instead a format known as the ebuild. Whereas RPM binaries are precompiled binaries, ebuilds are shell scripts with variables and functions which contain a description of the software, and instructions on how to obtain, configure, compile, and install it, more closely akin to (but more powerful than) the .spec files distributed in SRPMs.[8] The official repository provides over 19,600 ebuilds, the majority of which are distributed by the Gentoo mirrors. New and updated ebuilds can be obtained by synchronizing the local ebuild repositories with the mirrors. This is done by executing the command emaint sync -a. Historically, Gentoo has provided pre-compiled binary packages for many common programs, especially those which are lengthy to compile, such as Mozilla Firefox and OpenOffice.org. These are still installed with emerge, just by appending a "-bin" to the package name to instead install the binary version.
默认情况下，Gentoo 不像其他包管理系统（如 pacman 或 apt）那样使用二进制包，而是使用一种称为 ebuild 的格式。 RPM 二进制文件是预编译的二进制文件，而 ebuilds 是带有变量和函数的 shell 脚本，其中包含软件的描述，以及有关如何获取、配置、编译和安装软件的说明，更类似于（但更强大）.在 SRPM 中分发的规范文件。 [8]官方存储库提供超过 19,600 个 ebuild，其中大部分由 Gentoo 镜像分发。可以通过将本地 ebuild 存储库与镜像同步来获取新的和更新的 ebuild。这是通过执行命令 emaint sync -a 来完成的。历史上，Gentoo 为许多常见程序提供了预编译的二进制包，尤其是那些编译时间较长的程序，例如 Mozilla Firefox 和 OpenOffice.org。这些仍然与 emerge 一起安装，只是通过在包名称后附加一个“-bin”来代替安装二进制版本。
Gentoo does have a binary packaging format, which is a .tbz2 file (tar with bzip2 compression) with additional metadata. This feature enables the building of binary packages on one system (using Portage's buildpkg or quickpkg) followed by quick installation on compatible systems (with Portage's getbinpkg or emerge -K). See Portage Features in the Gentoo Linux Handbook for more information.
Gentoo 确实有二进制打包格式，它是一个带有附加元数据的 .tbz2 文件（tar 和 bzip2 压缩）。此功能允许在一个系统上构建二进制包（使用 Portage 的 buildpkg 或 quickpkg），然后在兼容系统上快速安装（使用 Portage 的 getbinpkg 或 emerge -K）。有关详细信息，请参阅 Gentoo Linux 手册中的 Portage 功能。
Masking is how Gentoo determines which packages are suitable for a system. Ebuilds designed for different architectures or experimental software are usually masked in a manner which prevents a stable system from installing them without user intervention.
屏蔽是 Gentoo 确定哪些包适合系统的方式。为不同架构或实验软件设计的 Ebuild 通常以某种方式被屏蔽，以防止稳定的系统在没有用户干预的情况下安装它们。
Packages that generally just require some testing but will often work fine are said to be keyword masked (i.e. they are available for systems with an ACCEPT_KEYWORDS make.conf entry starting with the character ~, such as ~x86, ~amd64, ~ppc). An individual keyword masked package can be unmasked by adding a line with the full package name and keyword to some file within the /etc/portage/package.accept_keywords/ directory. Users can make subdirectories here as well, allowing for custom organization. For example, if a masked package had multiple masked dependencies, the user could make a directory with the name of the original masked package, and put all the mask files for the package and its dependencies in that directory. This scheme replaces the older scheme of having /etc/portage/package.accept_keywords as one text file.
通常只需要一些测试但通常可以正常工作的软件包被称为关键字屏蔽（即它们可用于具有以字符 ~ 开头的 ACCEPT_KEYWORDS make.conf 条目的系统，例如 ~x86、~amd64、~ppc）。通过在 /etc/portage/package.accept_keywords/ 目录中的某个文件中添加一行带有完整包名称和关键字的行，可以取消屏蔽单个关键字屏蔽的包。用户也可以在这里创建子目录，允许自定义组织。例如，如果一个屏蔽包有多个屏蔽依赖项，用户可以用原始屏蔽包的名称创建一个目录，并将该包及其依赖项的所有屏蔽文件放在该目录中。该方案取代了将 /etc/portage/package.accept_keywords 作为一个文本文件的旧方案。
Packages with known problems or not considered mature enough to be candidates for stable are hard masked by one of the various package.mask files in /usr/portage/profiles, and such entries are generally accompanied by a comment from developers explaining the reason for the mask.
存在已知问题或被认为不够成熟以成为稳定候选者的软件包会被 /usr/portage/profiles 中的各种 package.mask 文件之一硬屏蔽，并且此类条目通常伴随着开发人员的评论，解释了出现问题的原因面具。
Gentoo/Alt is a project created to manage porting the portage framework and other features to other operating systems, such as Mac OS X and the freeBSDs. Gentoo/Alt was set up by Pieter Van den Abeele and Daniel Robbins after Pieter Van den Abeele founded Gentoo for Mac OS X.
Gentoo/Alt 是一个项目，用于管理将 portage 框架和其他功能移植到其他操作系统，例如 Mac OS X 和免费的 BSD。 Gentoo/Alt 是由 Pieter Van den Abeele 和 Daniel Robbins 在 Pieter Van den Abeele 为 Mac OS X 创立 Gentoo 之后成立的。
Gentoo for Mac OS X was the first non-Linux project of Gentoo and focused on making the Gentoo experience available on Apple's operating system by introducing the Portage system as a separate entity. This was roughly similar to Fink and MacPorts, but it used Portage instead of a Debian-like or Ports-like system. Later on, Gentoo for Mac OS X was made a subproject of Gentoo/Alt. The project is no longer active, because its prime assumption of using and not modifying the host OS appeared not to be realistic and eventually broke most packages or made them hardly maintainable. Gentoo for Mac OS X has been superseded by Gentoo Prefix, which is currently what Gentoo offers to Mac OS X users.[9]Gentoo for Mac OS X 是 Gentoo 的第一个非 Linux 项目，专注于通过将 Portage 系统作为一个单独的实体引入 Apple 操作系统，从而使 Gentoo 体验可用。这与 Fink 和 MacPorts 大致相似，但它使用 Portage 而不是类 Debian 或类 Ports 系统。后来，Gentoo for Mac OS X 成为 Gentoo/Alt 的子项目。该项目不再活跃，因为它使用而不修改主机操作系统的主要假设似乎不现实，最终破坏了大多数包或使它们难以维护。 Gentoo for Mac OS X 已经被 Gentoo Prefix 取代，这是目前 Gentoo 为 Mac OS X 用户提供的。 [9]
The Prefix project on Mac OS X is tested and supported on Mac OS X Tiger, Leopard and Snow Leopard on PowerPC, IA-32, and x86-64 architectures.[10]Mac OS X 上的 Prefix 项目在 PowerPC、IA-32 和 x86-64 架构的 Mac OS X Tiger、Leopard 和 Snow Leopard 上经过测试和支持。 [10]
Gentoo/FreeBSD brings the Gentoo Linux design, structure, and tools such as Portage and the Gentoo Linux base layout to the FreeBSD operating system. Gentoo's GNU toolchain is used instead of the original FreeBSD one.
Gentoo/FreeBSD 将 Gentoo Linux 设计、结构和工具（如 Portage 和 Gentoo Linux 基本布局）引入 FreeBSD 操作系统。使用 Gentoo 的 GNU 工具链代替原来的 FreeBSD 工具链。
Although the project is no longer maintained by any active Gentoo developers, there are instructions that allow installation of a full Gentoo/FreeBSD system.[11] FreeBSD system ebuilds are integrated into the main portage tree, but this port is far from being complete due to the amount of packages needing to be ported and the lack of a proper Live CD (FreeSBIE's Live CD or FreeBSD setup CD is used during installation).
尽管该项目不再由任何活跃的 Gentoo 开发人员维护，但仍有一些说明允许安装完整的 Gentoo/FreeBSD 系统。[11] FreeBSD 系统 ebuilds 已集成到主移植树中，但由于需要移植的软件包数量和缺少合适的 Live CD（安装过程中使用 FreeSBIE 的 Live CD 或 FreeBSD 安装 CD），此移植还远未完成.
The current (semi) official logo for Gentoo/FreeBSD is a daemonized "g", derived from original Gentoo Linux logo and inspired by the BSD Daemon. It was designed by Marius Morawski, responding to an unofficial contest launched by Diego Elio Pettenò on his blog.[13]Gentoo/FreeBSD 的当前（半）官方标志是一个守护进程化的“g”，源自原始的 Gentoo Linux 标志，并受到 BSD 守护进程的启发。它由 Marius Morawski 设计，响应 Diego Elio Petteno 在他的博客上发起的非官方竞赛。 [13]
Gentoo/NetBSD is a project to provide a GNUuserland managed by Portage with a NetBSD kernel. The project was started by Damian Florczyk. Only the x86 architecture is targeted and the system as a whole is in an incomplete state.
Gentoo/NetBSD 是一个提供由 Portage 管理的带有 NetBSD 内核的 GNU 用户区的项目。该项目由 Damian Florczyk 发起。仅针对 x86 架构，整个系统处于不完整状态。
Gentoo/OpenBSD is a Gentoo/*BSD subproject to port Gentoo features such as Portage to the OpenBSD operating system. It was originally started by Grant Goodyear and is currently[when?] on development hiatus. An ISO image based on OpenBSD 3.8 is currently maintained by Karol Pasternak and can be downloaded from the project's web site.
Gentoo/OpenBSD 是一个 Gentoo/*BSD 子项目，用于将 Gentoo 功能（例如 Portage）移植到 OpenBSD 操作系统。它最初由 Grant Goodyear 发起，目前 [什么时候？] 处于开发中断状态。基于 OpenBSD 3.8 的 ISO 映像目前由 Karol Pasternak 维护，可以从该项目的网站下载。
Gentoo/DragonFlyBSD is a currently[when?] unofficial port to the DragonFlyBSD kernel. The project is developed by Robert Sebastian Gerus.[14]Gentoo/DragonFlyBSD 是当前[何时？] DragonFlyBSD 内核的非官方端口。该项目由 Robert Sebastian Gerus 开发。 [14]
Led by Benda Xu, "Gentoo RAP for Android Devices" installs a variant of Gentoo called Gentoo RAP in a directory prefix alongside Android.[16] The Linux kernel is used by both Android and Gentoo RAP.[16]在 Benda Xu 的带领下，“Gentoo RAP for Android Devices”在 Android 旁边的目录前缀中安装了一个名为 Gentoo RAP 的 Gentoo 变体。 [16] Android 和 Gentoo RAP 都使用 Linux 内核。 [16]
Gentoo/Interix (eprefix) is a port of Gentoo that runs atop the Interix Subsystem for Windows which is also known as Microsoft Windows Services for UNIX (SFU) or Subsystem for Unix-based Applications (SUA). A result of the Gentoo/Interix project is the ability to install and use the Portage system to emerge native Windows applications (requires Visual Studio, 2008 Express Edition will do too). However, this feature does not support the wide variety of packages supported by other platforms (including Interix).
Gentoo/Interix (eprefix) 是 Gentoo 的一个端口，它运行在 Windows 的 Interix 子系统之上，也称为 Microsoft Windows Services for UNIX (SFU) 或 Subsystem for Unix-based Applications (SUA)。 Gentoo/Interix 项目的一个结果是能够安装和使用 Portage 系统来生成原生 Windows 应用程序（需要 Visual Studio，2008 Express Edition 也可以）。但是，此功能不支持其他平台（包括 Interix）支持的各种包。
An unofficial port to the Solaris operating system, "Portaris", was announced around 2006, but never got into a public state. It was superseded by the Gentoo Prefix project.
Solaris 操作系统“Portaris”的非官方端口于 2006 年左右宣布，但从未进入公开状态。它被 Gentoo Prefix 项目所取代。
Started in 2011 as a Google Summer of Code project, Plan 9 For Gentoo takes the Gentoo base and overlays a userspace inspired by Plan 9.[17] The stated objectives of the project are to have better hardware support, better software support and to create a "culture shock" for people that have previously used Linux systems.[17] The project is maintained by Robert Seaton.[17]始于 2011 年的 Google Summer of Code 项目，Plan 9 For Gentoo 采用 Gentoo 基础并覆盖受 Plan 9 启发的用户空间。 [17]该项目的既定目标是提供更好的硬件支持、更好的软件支持，并为以前使用过 Linux 系统的人们创造一种“文化冲击”。 [17]该项目由 Robert Seaton 维护。 [17]
^"repo/gentoo.git". gitweb.gentoo.org. Archived from the original on 2021-12-05. Retrieved 2022-12-18.^ “repo/gentoo.git”。 gitweb.gentoo.org。原始存档于 2021-12-05。检索于 2022-12-18。
^"About Gentoo". gentoo.org. Archived from the original on December 21, 2018. Retrieved August 23, 2019.^ “关于 Gentoo”。 gentoo.org。原始存档于 2018 年 12 月 21 日。检索于 2019 年 8 月 23 日。
^Daniel Robbins (10 October 2002). "Gentoo Linux Reloaded - O'Reilly Media". Archived from the original on 14 October 2017. Retrieved 27 May 2015.^ 丹尼尔·罗宾斯（2002 年 10 月 10 日）。 “Gentoo Linux Reloaded - O'Reilly Media”。原始存档于 2017 年 10 月 14 日。2015 年 5 月 27 日检索。
^"OSNews.com". Archived from the original on 29 September 2007. Retrieved 27 May 2015.^ “OSNews.com”。原始存档于 2007 年 9 月 29 日。2015 年 5 月 27 日检索。
^"Project:Package Manager Specification". wiki.gentoo.org. Archived from the original on July 8, 2019. Retrieved August 23, 2019.^ “项目：包管理器规范”。 wiki.gentoo.org。原始存档于 2019 年 7 月 8 日。检索于 2019 年 8 月 23 日。
^"ebuild - Gentoo Wiki". wiki.gentoo.org. Archived from the original on 2019-12-17. Retrieved 2019-12-17.^ “ebuild - Gentoo Wiki”。 wiki.gentoo.org。原始存档于 2019-12-17。检索于 2019-12-17。
^Groffen, Fabian (2005-12-15). "Gentoo for Mac OS X project targets". Archived from the original on 2008-05-21. Retrieved 2017-07-20.^ 格罗芬，法比安 (2005-12-15)。 “Gentoo for Mac OS X 项目目标”。原始存档于 2008-05-21。检索于 2017-07-20。
^ Jump up to: abcd"Gentoo FreeBSD". Gentoo Wiki. 2018-08-20. Archived from the original on 2014-01-06. Retrieved 2019-03-06.^ 跳转至： a b c d “Gentoo FreeBSD”。 Gentoo 维基百科。 2018-08-20.原始存档于 2014-01-06。检索于 2019-03-06。
^"Index of /experimental/bsd/freebsd/stages/amd64-fbsd-9.1". Distfiles.gentoo.org. 2013-07-07. Archived from the original on 2016-09-27. Retrieved 2016-09-24.^ “/experimental/bsd/freebsd/stages/amd64-fbsd-9.1 的索引”。 Distfiles.gentoo.org。 2013-07-07。原始存档于 2016-09-27。检索于 2016-09-24。
^Pettenò, Diego Elio (2005-07-16). "Not-so-official Gentoo/FreeBSD artwork contest". Flameeyes's Weblog. Archived from the original on 2019-04-19. Retrieved 2017-07-20.^ Pettenò, Diego Elio (2005-07-16)。 “非官方的 Gentoo/FreeBSD 艺术作品竞赛”。 Flameeyes 的博客。原始存档于 2019-04-19。检索于 2017-07-20。
^Goodyear, Grant; Pettenò, Diego Elio (2006-10-19). "Gentoo/*BSD". Archived from the original on 2007-12-28. Retrieved 2017-07-20.^ 固特异，格兰特；佩泰诺，迭戈·埃里奥 (2006-10-19)。 “Gentoo/*BSD”。原始存档于 2007-12-28。检索于 2017-07-20。
^"Gentoo GNU HURD". Archived from the original on 2010-01-09. Retrieved 2017-07-20.^ “Gentoo GNU 赫德”。原始存档于 2010-01-09。检索于 2017-07-20。
^ Jump up to: ab"Project:Android - Gentoo Wiki". Wiki.gentoo.org. 2016-01-13. Archived from the original on 2016-10-24. Retrieved 2016-09-24.^ 跳转至： a b “Project:Android - Gentoo Wiki”。维基.gentoo.org。 2016-01-13。原始存档于 2016-10-24。检索于 2016-09-24。
Organization supporting the free software movement
This article may contain an excessive amount of intricate detail that may interest only a particular audience. Please help by spinning off or relocating any relevant information, and removing excessive detail that may be against Wikipedia's inclusion policy.(March 2022) (Learn how and when to remove this template message)这篇文章可能包含过多的复杂细节，可能只有特定的读者感兴趣。请通过拆分或重新定位任何相关信息来提供帮助，并删除可能违反维基百科收录政策的过多细节。 （2022 年 3 月）（了解如何以及何时删除此模板消息）
Free Software Foundation自由软件基金会
Free Software Foundation logo自由软件基金会徽标
Abbreviation缩写
FSF金融稳定基金
Formation队形
October 4, 1985; 37 years ago ()[1]1985 年 10 月 4 日； 37年前[1]
The Free Software Foundation (FSF) is a 501(c)(3)non-profit organization founded by Richard Stallman[6] on October 4, 1985, to support the free software movement, with the organization's preference for software being distributed under copyleft ("share alike") terms,[7] such as with its own GNU General Public License.[8] The FSF was incorporated in Boston,[9]Massachusetts, US, where it is also based.[10]自由软件基金会 (FSF) 是 501(c)(3) 非营利组织，由 Richard Stallman[6] 于 1985 年 10 月 4 日创立，旨在支持自由软件运动，该组织偏爱在 copyleft 下分发的软件（“相同方式共享”）条款，[7] 例如它自己的 GNU 通用公共许可证。 [8] FSF 成立于波士顿，[9] 美国马萨诸塞州，它也位于那里。 [10]
From its founding until the mid-1990s, FSF's funds were mostly used to employ software developers to write free software for the GNU Project. Since the mid-1990s, the FSF's employees and volunteers have mostly worked on legal and structural issues for the free software movement and the free software community.
从成立到 20 世纪 90 年代中期，FSF 的资金主要用于聘请软件开发人员为 GNU 项目编写自由软件。自 20 世纪 90 年代中期以来，FSF 的员工和志愿者主要致力于自由软件运动和自由软件社区的法律和结构问题。
Consistent with its goals, the FSF aims to use only free software on its own computers.[11]与其目标一致，FSF 旨在仅在其自己的计算机上使用自由软件。 [11]
The Free Software Foundation was founded in 1985 as a non-profit corporation supporting free software development. It continued existing GNU projects such as the sale of manuals and tapes, and employed developers of the free software system.[12] Since then, it has continued these activities, as well as advocating for the free software movement. The FSF is also the steward of several free software licenses, meaning it publishes them and has the ability to make revisions as needed.[13]自由软件基金会成立于 1985 年，是一家支持自由软件开发的非营利性公司。它继续现有的 GNU 项目，例如销售手册和磁带，并雇用自由软件系统的开发人员。 [12]从那时起，它继续开展这些活动，并倡导自由软件运动。 FSF 还是多个自由软件许可的管理者，这意味着它发布它们并有能力根据需要进行修订。 [13]
The FSF holds the copyrights on many pieces of the GNU system, such as GNU Compiler Collection. As holder of these copyrights, it has the authority to enforce the copyleft requirements of the GNU General Public License (GPL) when copyright infringement occurs on that software.
FSF 拥有 GNU 系统许多部分的版权，例如 GNU Compiler Collection。作为这些版权的持有者，当该软件发生版权侵权时，它有权执行 GNU 通用公共许可证 (GPL) 的 copyleft 要求。
From 1991 until 2001, GPL enforcement was done informally, usually by Stallman himself, often with assistance from FSF's lawyer, Eben Moglen.[citation needed] Typically, GPL violations during this time were cleared up by short email exchanges between Stallman and the violator.[citation needed] In the interest of promoting copyleft assertiveness by software companies to the level that the FSF was already doing, in 2004 Harald Welte launched gpl-violations.org.
从 1991 年到 2001 年，GPL 的执行是非正式的，通常由 Stallman 本人，通常在 FSF 的律师 Eben Moglen 的协助下进行。[需要引证]通常，在这段时间里，GPL 的违规行为是通过 Stallman 和违规者之间的简短电子邮件交流来解决的。 [需要引用] 为了将软件公司的 copyleft 自信提升到 FSF 已经在做的水平，Harald Welte 在 2004 年推出了 gpl-violations.org。
In late 2001, Bradley M. Kuhn (then executive director), with the assistance of Moglen, David Turner, and Peter T. Brown, formalized these efforts into FSF's GPL Compliance Labs. From 2002–2004, high-profile GPL enforcement cases, such as those against Linksys and OpenTV, became frequent.[14][15][16]2001 年底，Bradley M. Kuhn（当时的执行董事）在 Moglen、David Turner 和 Peter T. Brown 的协助下，将这些努力正式纳入 FSF 的 GPL 合规实验室。从 2002 年到 2004 年，备受瞩目的 GPL 执法案件（例如针对 Linksys 和 OpenTV 的案件）变得频繁。[14][15][16]
GPL enforcement and educational campaigns on GPL compliance was a major focus of the FSF's efforts during this period.[17][18]GPL 强制执行和关于 GPL 合规性的教育活动是 FSF 在此期间的主要工作重点。 [17][18]
In March 2003, SCO filed suit against IBM alleging that IBM's contributions to various free software, including FSF's GNU, violated SCO's rights. While FSF was never a party to the lawsuit, FSF was subpoenaed on November 5, 2003.[19] During 2003 and 2004, FSF put substantial advocacy effort into responding to the lawsuit and quelling its negative impact on the adoption and promotion of free software.[20][21]2003 年 3 月，SCO 对 IBM 提起诉讼，指控 IBM 对各种自由软件（包括 FSF 的 GNU）的贡献侵犯了 SCO 的权利。虽然 FSF 从未参与诉讼，但 FSF 于 2003 年 11 月 5 日被传唤。 [19]在 2003 年和 2004 年期间，FSF 投入了大量的宣传努力来回应诉讼并平息其对自由软件的采用和推广的负面影响。 [20][21]
From 2003 to 2005, FSF held legal seminars to explain the GPL and the surrounding law.[22] Usually taught by Bradley M. Kuhn and Daniel Ravicher, these seminars offered CLE credit and were the first effort to give formal legal education on the GPL.[21][23][24]从 2003 年到 2005 年，FSF 举办了法律研讨会来解释 GPL 和相关法律。 [22]通常由 Bradley M. Kuhn 和 Daniel Ravicher 教授，这些研讨会提供 CLE 学分，并且是对 GPL 进行正规法律教育的首次尝试。 [21][23][24]
In 2007, the FSF published the third version of the GNU General Public License after significant outside input.[25][26]2007 年，FSF 在大量外部输入后发布了第三版 GNU 通用公共许可证。[25][26]
In December 2008, FSF filed a lawsuit against Cisco for using GPL-licensed components shipped with Linksys products. Cisco was notified of the licensing issue in 2003 but Cisco repeatedly disregarded its obligations under the GPL.[27] In May 2009, FSF dropped the lawsuit when Cisco agreed to make a monetary donation to the FSF and appoint a Free Software Director to conduct continuous reviews of the company's license compliance practices.[28]2008 年 12 月，FSF 对思科使用 Linksys 产品附带的 GPL 许可组件提起诉讼。思科在 2003 年被告知许可问题，但思科一再无视其在 GPL 下的义务。 [27] 2009 年 5 月，当思科同意向 FSF 捐款并任命自由软件总监对公司的许可合规实践进行持续审查时，FSF 撤销了诉讼。 [28]
In September 2019, Richard Stallman resigned as president of the FSF after pressure from journalists and members of the open source community in response to him making controversial comments in defense of then-deceased Marvin Minsky on Jeffrey Epstein's sex trafficking scandal.[29] Nevertheless, Stallman remained head of the GNU Project and in 2021, he returned to the FSF board of directors.[30][31][32][33]2019 年 9 月，理查德·斯托曼在记者和开源社区成员的压力下辞去了自由软件基金会主席的职务，以回应他在杰弗里·爱泼斯坦的性交易丑闻中为当时已故的马文·明斯基辩护而发表有争议的评论。 [29]尽管如此，斯托曼仍然是 GNU 项目的负责人，并于 2021 年重返 FSF 董事会。[30][31][32][33]
Current and ongoing activities[edit]当前和正在进行的活动[编辑]
The original purpose of the FSF was to promote the ideals of free software. The organization developed the GNU operating system as an example of this.
FSF 的最初目的是促进自由软件的理想。该组织开发了 GNU 操作系统作为这方面的一个例子。
The FSF's publishing department, responsible for "publishing affordable books on computer science using freely distributable licenses."[34][35]FSF 的出版部门，负责“使用可自由分发的许可证出版负担得起的计算机科学书籍。”[34][35]
This is a listing of software packages that have been verified as free software. Each package entry contains up to 47 pieces of information such as the project's homepage, developers, programming language, etc. The goals are to provide a search engine for free software, and to provide a cross-reference for users to check if a package has been verified as being free software. FSF has received a small amount of funding from UNESCO for this project.
这是已验证为免费软件的软件包列表。每个包条目最多包含项目的主页、开发者、编程语言等47条信息。目标是提供一个免费软件的搜索引擎，并为用户提供交叉引用以检查包是否有被验证为自由软件。 FSF 为该项目从教科文组织获得了少量资金。
Maintaining the Free Software Definition[edit]维护自由软件定义[编辑]
An abbreviation for "Hardware-Node", the h-node website lists hardware and device drivers that have been verified as compatible with free software. It is user-edited and volunteer supported with hardware entries tested by users before publication.[36][37][38]h-node 网站是“Hardware-Node”的缩写，列出了经验证与免费软件兼容的硬件和设备驱动程序。它由用户编辑并由志愿者支持，并在发布前由用户测试硬件条目。[36][37][38]
FSF sponsors a number of campaigns against what it perceives as dangers to software freedom, including software patents, digital rights management (which the FSF and others[39] have re-termed "digital restrictions management", as part of its effort to highlight technologies that are "designed to take away and limit your rights,"[40]) and user interface copyright. Defective by Design is an FSF-initiated campaign against DRM. It also has a campaign to promote Ogg+Vorbis, a free alternative to proprietary formats like AAC and MQA. FSF also sponsors free software projects it deems "high-priority".
FSF 赞助了一系列运动来反对它认为对软件自由的威胁，包括软件专利、数字版权管理（FSF 和其他人[39] 将其重新命名为“数字限制管理”，作为其强调技术的努力的一部分“旨在剥夺和限制您的权利，”[40]）和用户界面版权。 Defective by Design 是 FSF 发起的反对 DRM 的活动。它还开展了一项推广 Ogg+Vorbis 的活动，Ogg+Vorbis 是 AAC 和 MQA 等专有格式的免费替代品。 FSF 还赞助它认为“高度优先”的自由软件项目。
The LibrePlanet wiki organizes FSF members into regional groups in order to promote free software activism against Digital Restrictions Management and other issues promoted by the FSF.
LibrePlanet wiki 将 FSF 成员组织成区域组，以促进针对数字限制管理和 FSF 推动的其他问题的自由软件活动。
The FSF maintains a list of "high priority projects" to which the Foundation claims that "there is a vital need to draw the free software community's attention".[41] The FSF considers these projects "important because computer users are continually being seduced into using non-free software, because there is no adequate free replacement."[41]FSF 维护着一份“高优先级项目”的清单，基金会声称“迫切需要引起自由软件社区的注意”。[41] FSF 认为这些项目“很重要，因为计算机用户不断被引诱使用非自由软件，因为没有足够的免费替代品。”[41]
The effort has been criticized by Michael Larabel for either not instigating active development or for being slow at the work being done, even after certain projects were added to the list.[43][44]Michael Larabel 批评这项工作要么没有鼓励积极的开发，要么工作进展缓慢，即使在某些项目被添加到列表中之后也是如此。 [43][44]
The FSF maintains a "Respects Your Freedom" (RYF) hardware certification program. To be granted certification, a product must use 100% Free Software, allow user installation of modified software, be free of backdoors and conform with several other requirements.[46]FSF 维护“尊重您的自由”(RYF) 硬件认证计划。要获得认证，产品必须使用 100% 自由软件，允许用户安装修改后的软件，没有后门并符合其他几项要求。 [46]
The FSF's board of directors includes professors at leading universities, senior engineers, and founders. Current board members are:[47]FSF 的董事会包括一流大学的教授、高级工程师和创始人。目前的董事会成员是：[47]
Geoffrey Knauth, senior software engineer at SFA, Inc. (served since October 23, 1997)Geoffrey Knauth，SFA, Inc. 高级软件工程师（自 1997 年 10 月 23 日起任职）
Henry Poole, founder of CivicActions, a government digital services firm (served since December 12, 2002)Henry Poole，政府数字服务公司 CivicActions 的创始人（自 2002 年 12 月 12 日起任职）
Alexander Oliva, Vice President (served since August 28, 2019)[50]亚历山大·奥利瓦，副总裁（自2019年8月28日起任职）[50]
Hal Abelson, founding member,[51] professor of computer science at the Massachusetts Institute of Technology (served from inception until March 5, 1998, and rejoined circa 2005)Hal Abelson，创始成员，[51] 麻省理工学院计算机科学教授（从成立到 1998 年 3 月 5 日，大约在 2005 年重新加入）
Robert J. Chassell, founding treasurer,[51] as well as a founding director (served from inception until June 3, 1997)Robert J. Chassell，创始财务主管，[51] 以及创始董事（从成立到 1997 年 6 月 3 日）
Miguel de Icaza (served from August 1999[note 1] until February 25, 2002[52])Miguel de Icaza（1999年8月[注1]至2002年2月25日[52]任职）
Benjamin Mako Hill, assistant professor at the University of Washington (served from July 25, 2007 until October 2019)[citation needed]Benjamin Mako Hill，华盛顿大学助理教授（2007 年 7 月 25 日至 2019 年 10 月任职）[需要引证]
Matthew Garrett, software developer (served since October 16, 2014)[53]Matthew Garrett，软件开发人员（自 2014 年 10 月 16 日起任职）[53]
Bradley Kuhn, executive director of the Software Freedom Conservancy and FSF's former executive director (served from March 25, 2010[54] to Oct 13, 2019[55])Bradley Kuhn，软件自由保护协会执行理事，FSF前执行理事（任职时间：2010年3月25日[54]至2019年10月13日[55]）
Lawrence Lessig, professor of law at Stanford University (served from March 28, 2004 until 2008)Lawrence Lessig，斯坦福大学法学教授（2004年3月28日至2008年任职）
Eben Moglen (served from July 28, 2000[note 2] until 2007[56])Eben Moglen（2000年7月28日[注2]至2007年[56]任职）
Len Tower Jr., founding member,[51] (served until September 2, 1997)Len Tower Jr.，创始成员，[51]（任期至 1997 年 9 月 2 日）
Kat Walsh, copyright and technology attorney, free culture and free software advocate, and former chair of the Wikimedia Foundation. She joined the board in 2015.[57] She voted against the readmittance of Richard Stallman to the board and, on March 25, 2021, resigned saying "It's a decision that has been a long time coming for me".[58]Kat Walsh，版权和技术律师，自由文化和自由软件倡导者，维基媒体基金会前任主席。她于 2015 年加入董事会。 [57]她投票反对让理查德·斯托曼重新加入董事会，并于 2021 年 3 月 25 日辞职，称“这是我等了很长时间的决定”。[58]
At any given time, there are usually around a dozen employees.[62] Most, but not all, work at the FSF headquarters in Boston, Massachusetts.[63]在任何时候，通常都有十几名员工。 [62]大多数（但不是全部）在马萨诸塞州波士顿的 FSF 总部工作。 [63]
On November 25, 2002, the FSF launched the FSF Associate Membership program for individuals.[64] Bradley M. Kuhn (FSF executive director, 2001–2005) launched the program and also signed up as the first Associate Member[65]2002 年 11 月 25 日，FSF 启动了针对个人的 FSF 准会员计划。 [64] Bradley M. Kuhn（FSF 执行董事，2001-2005 年）启动了该计划，并成为第一位准会员[65]
Associate members are primarily an honorary and funding support role.[61] In 2023, associate members gained the ability to make board nominations, along with FSF staff and FSF voting members. There is also an annual meeting of FSF members, usually during lunch at LibrePlanet, in which feedback for FSF is solicited.
准会员主要是名誉和资金支持角色。 [61] 2023 年，准成员以及 FSF 工作人员和 FSF 投票成员获得了提名董事会的能力。还有一个 FSF 成员年会，通常是在 LibrePlanet 的午餐时间，会上征求对 FSF 的反馈。
Eben Moglen and Dan Ravicher previously served individually as pro bono legal counsel to the FSF. After forming the Software Freedom Law Center, Eben Moglen continued to serve as the FSF's general counsel until 2016.[66]Eben Moglen 和 Dan Ravicher 之前分别担任 FSF 的无偿法律顾问。在组建软件自由法律中心后，Eben Moglen 继续担任 FSF 的总法律顾问，直到 2016 年。 [66]
Most of the FSF funding comes from patrons and members.[67] Revenue streams also come from free-software-related compliance labs, job postings, published works, and a web store. FSF offers speakers and seminars for pay, and all FSF projects accept donations.
FSF 的大部分资金来自赞助人和会员。 [67]收入流还来自与自由软件相关的合规实验室、职位发布、已出版的作品和网上商店。 FSF 提供有偿演讲者和研讨会，所有 FSF 项目都接受捐款。
Revenues fund free-software programs and campaigns, while cash is invested conservatively in socially responsible investing. The financial strategy is designed to maintain the Foundation's long-term future through economic stability.
收入为免费软件计划和活动提供资金，而现金则保守地投资于对社会负责的投资。财务战略旨在通过经济稳定维持基金会的长期未来。
The FSF is a tax-exempt organization and posts annual IRS Form 990 filings online.[68]FSF 是一个免税组织，每年在线发布 IRS 990 表格文件。 [68]
Linus Torvalds has criticized FSF for using GPLv3 as a weapon in the fight against DRM. Torvalds argues that the issue of DRM and that of a software license should be treated as two separate issues.[69]Linus Torvalds 批评 FSF 使用 GPLv3 作为对抗 DRM 的武器。 Torvalds 认为 DRM 问题和软件许可证问题应该被视为两个不同的问题。 [69]
Defective by Design campaign[edit]Defective by Design 活动[编辑]
On June 16, 2010, Joe Brockmeier, a journalist at Linux Magazine, criticized the Defective by Design campaign by the FSF as "negative" and "juvenile" and not being adequate for providing users with "credible alternatives" to proprietary software.[70] FSF responded to this criticism by saying "that there is a fundamental difference between speaking out against policies or actions and smear campaigns", and "that if one is taking an ethical position, it is justified, and often necessary, to not only speak about the benefits of freedom but against acts of dispossession and disenfranchisement."[71]2010 年 6 月 16 日，Linux 杂志的记者 Joe Brockmeier 批评 FSF 的“设计缺陷”运动是“消极的”和“幼稚的”，不足以为用户提供专有软件的“可靠替代品”。 [70 ] FSF 回应了这一批评，称“公开反对政策或行动与抹黑运动之间存在根本区别”，并且“如果一个人采取道德立场，那么不仅谈论自由的好处，但反对剥夺和剥夺权利的行为。”[71]
GNU LibreDWG license controversy[edit]GNU LibreDWG 许可证争议[编辑]
In 2009, a license update of LibDWG/LibreDWG to the version 3 of the GNU GPL,[72] made it impossible for the free software projects LibreCAD and FreeCAD to use LibreDWG legally.[73] Many projects voiced their unhappiness about the GPLv3 license selection for LibreDWG, such as FreeCAD, LibreCAD, Assimp, and Blender.[74] Some suggested the selection of a license with a broader license compatibility, for instance the MIT, BSD, or LGPL 2.1.[74] A request went to the FSF to relicense GNU LibreDWG as GPLv2, which was rejected in 2012.[75]2009 年，LibDWG/LibreDWG 的许可证更新为 GNU GPL 的第 3 版，[72] 使得自由软件项目 LibreCAD 和 FreeCAD 无法合法使用 LibreDWG。 [73]许多项目表达了他们对 LibreDWG 选择 GPLv3 许可证的不满，例如 FreeCAD、LibreCAD、Assimp 和 Blender。 [74]一些人建议选择具有更广泛许可证兼容性的许可证，例如 MIT、BSD 或 LGPL 2.1。 [74]向 FSF 提出将 GNU LibreDWG 重新授权为 GPLv2 的请求，该请求在 2012 年被拒绝。 [75]
The libDWG has stalled since 2011 for various reasons, including license issues.[76]libDWG 自 2011 年以来由于各种原因停滞不前，包括许可证问题。 [76]
Accusations against Richard Stallman[edit]对理查德·斯托曼的指控[编辑]
In 2019 Richard Stallman replied to an internal MIT mailing list post to criticize a statement claiming that Marvin Minsky harmed one of Jeffrey Epstein's victims. The poster of the email responded by publishing the email on a blog along with some stories which vaguely painted RMS as a misogynist. The accusations were later publicly rebuked by multiple people.[77] As a result of widespread negative media coverage, Stallman resigned as the FSF president and an FSF board member. However, he remained an FSF voting member, an FSF volunteer, and the head of the GNU Project, which FSF dedicates a significant portion of its resources to supporting. There was no public indication as to whether he continued to participate in FSF board meetings as a guest.
2019 年，理查德·斯托曼 (Richard Stallman) 回复麻省理工学院内部邮件列表帖子，批评一份声称马文·明斯基 (Marvin Minsky) 伤害了杰弗里·爱泼斯坦 (Jeffrey Epstein) 的一名受害者的声明。作为回应，发帖者在博客上发布了该电子邮件以及一些模糊地将 RMS 描绘成厌恶女性的故事。这些指控后来遭到多人公开谴责。 [77]由于广泛的负面媒体报道，斯托曼辞去了 FSF 主席和 FSF 董事会成员的职务。然而，他仍然是 FSF 的投票成员、FSF 志愿者和 GNU 项目的负责人，FSF 将其大部分资源用于支持该项目。没有公开迹象表明他是否继续作为嘉宾参加 FSF 董事会会议。
Stallman rejoined the board 18 months later but remained stepped down from the presidency. News stories implied that he had left the FSF in general and had now returned.[78] He joined as one of 7 board members. The FSF by-laws define the president as a chief executive officer.[79] Stallman announced he had rejoined the board during a talk at LibrePlanet in blithe manner. Several prominent organizations and individuals who develop free software objected to the decision of him rejoining the board, citing past writings on Stallman's blog which they considered antithetical to promoting a diverse community.[80][81] As a result of Stallman's reinstatement Red Hat announced that it would stop donating to the Free Software Foundation.[80][82] However, the FSF quickly announced that less than 3% of its funding came from direct corporate support and that it was in good financial health.[83]18 个月后，斯托曼重新加入董事会，但仍辞去了总裁一职。新闻报道暗示他已经离开了 FSF，现在又回来了。 [78]他作为 7 名董事会成员之一加入。 FSF 章程将总裁定义为首席执行官。 [79] Stallman 在 LibrePlanet 的一次演讲中愉快地宣布他已重新加入董事会。一些开发自由软件的著名组织和个人反对他重新加入董事会的决定，并引用了 Stallman 博客上的过去文章，他们认为这些文章与促进多元化社区背道而驰。 [80][81]由于 Stallman 复职，Red Hat 宣布将停止向自由软件基金会捐款。[80][82]然而，FSF 很快宣布其资金中只有不到 3% 来自直接的企业支持，并且其财务状况良好。 [83]
The FSF staff were not expecting Stallman's announcement and after it drew negative attention, some resigned. The board enacted a series of reforms in the aftermath. They included a code of ethics, a union elected staff seat on the board, a transparent community informed process of electing new board members to be followed by a community informed review of existing board members. FSF hired 3 new staff by summer 2022. By that time, it had one staff position unfilled and one filled part time out of 13 full time staff positions.[citation needed]FSF 的工作人员没有预料到 Stallman 的声明，在它引起负面关注后，一些人辞职了。董事会随后实施了一系列改革。其中包括道德准则、工会选举产生的董事会工作人员席位、透明的社区知情流程选举新董事会成员，然后对现有董事会成员进行社区知情审查。到 2022 年夏季，FSF 雇佣了 3 名新员工。到那时，在 13 个全职员工职位中，有 1 个职位空缺，1 个填补了兼职职位。[引证需要]
This section needs expansion. You can help by adding to it. (May 2014)这部分需要扩展。您可以通过添加它来提供帮助。 （2014 年 5 月）
Key players and industries that have made honorific mention and awards include:
获得荣誉提名和奖项的主要参与者和行业包括：
2001: GNU Project received the USENIX Lifetime Achievement Award for "the ubiquity, breadth, and quality of its freely available redistributable and modifiable software, which has enabled a generation of research and commercial development".[84]2001 年：GNU 项目获得 USENIX 终身成就奖，以表彰“其免费提供的可再发行和可修改软件的普遍性、广度和质量，这促成了一代人的研究和商业开发”。[84]
2005: Prix Ars Electronica Award of Distinction in the category of "Digital Communities"[85]2005 年：Prix Ars Electronica“数字社区”类别杰出奖[85]
^The FSF annual filings with the Commonwealth of Massachusetts for 1998 and
1999 show that De Icaza was not on the board on 1998-11-01 and was as of 1999-11-01, so he clearly joined sometime between those dates. Those documents further indicate that the 1999 annual meeting occurred in August; usually, new directors are elected at annual meetings.^ 1998 年和 1999 年向马萨诸塞联邦提交的 FSF 年度文件显示，De Icaza 在 1998 年 11 月 1 日不在董事会，但截至 1999 年 11 月 1 日，他显然是在这些日期之间的某个时间加入的。这些文件进一步表明，1999 年年会是在 8 月召开的；通常，新董事是在年会上选出的。
^The FSF annual filings with the Commonwealth of Massachusetts for 1999 and 2000 show that Moglen was not on the board on November 1, 1999, and was as of November 1, 2000, so he clearly joined sometime between those dates. Those documents further indicate that the 2000 annual meeting occurred on July 28, 2000; usually, new directors are elected at annual meetings.^ 1999 年和 2000 年向马萨诸塞联邦提交的 FSF 年度文件显示，莫格伦在 1999 年 11 月 1 日不在董事会，但截至 2000 年 11 月 1 日，他显然是在这两个日期之间的某个时间加入的。这些文件进一步表明，2000 年年会于 2000 年 7 月 28 日举行；通常，新董事是在年会上选出的。
^Roberts, Ken Schwencke, Mike Tigas, Sisi Wei, Alec Glassford, Andrea Suozzo, Brandon (2013-05-09). "Free Software Foundation Inc - Nonprofit Explorer". ProPublica. Retrieved 2022-09-13.^ Roberts, Ken Schwencke, Mike Tigas, Sisi Wei, Alec Glassford, Andrea Suozzo, Brandon (2013-05-09)。 “自由软件基金会 - 非营利探索者”。公众号。检索于 2022-09-13。
^Roberts, Ken Schwencke, Mike Tigas, Sisi Wei, Alec Glassford, Andrea Suozzo, Brandon (2013-05-09). "Free Software Foundation Inc – Nonprofit Explorer". ProPublica. Retrieved 2022-09-13.^ Roberts, Ken Schwencke, Mike Tigas, Sisi Wei, Alec Glassford, Andrea Suozzo, Brandon (2013-05-09)。 “Free Software Foundation Inc – Nonprofit Explorer”。公众号。检索于 2022-09-13。
^"FREE SOFTWARE FOUNDATION, INC. Summary Screen". The Commonwealth of Massachusetts, Secretary of the Commonwealth, Corporations Division. Archived from the original on 2013-05-25.^ “FREE SOFTWARE FOUNDATION, INC. 摘要屏幕”。马萨诸塞州联邦公司司司长。原始存档于 2013-05-25。
^Stallman, Richard M. (2002). "Linux, GNU, and freedom". Philosophy of the GNU Project. GNU Project. Retrieved 2006-12-10.^ Stallman, Richard M. (2002)。 “Linux、GNU 和自由”。 GNU 项目的哲学。 GNU 项目。检索于 2006-12-10。
^"The GNU Project". Free Software Foundation. Retrieved June 24, 2012.^ “GNU 计划”。自由软件基金会。 2012 年 6 月 24 日检索。
^Meeker, Heather (2005-06-28). "The Legend of Linksys". Archived from the original on 2009-04-19. Retrieved 2007-08-11. Hosted on the Wayback Machine.^ Meeker, Heather (2005-06-28)。 “Linksys 的传奇”。原始存档于 2009-04-19。检索于 2007-08-11。托管在 Wayback Machine 上。
^Gillmor, Dan (2003-05-21). "GPL Legal Battle Coming?". SiliconValley.com (a division of the San Jose Mercury News). Archived from the original on 2003-05-24. Retrieved 2007-08-11.^ Gillmor, Dan (2003-05-21)。 “GPL 法律战即将来临？”。 SiliconValley.com（圣何塞水星报的一个部门）。原始存档于 2003-05-24。检索于 2007-08-11。
^Kuhn, Bradley M. (June 2003). "FSF Bulletin Issue 2, June 2003". Free Software Foundation. Retrieved 2008-07-04. On Friday 8 August 2003, we will hold a seminar on the GNU GPL. The seminar, titled "Free Software Licensing and the GNU GPL", will be co-led by Daniel Ravicher, Outside Counsel to FSF from Patterson Belknap Webb & Tyler, and Bradley M. Kuhn, Executive Director of FSF.^ Kuhn, Bradley M.（2003 年 6 月）。 “FSF 公告第 2 期，2003 年 6 月”。自由软件基金会。检索于 2008-07-04。 2003 年 8 月 8 日星期五，我们将举办一个关于 GNU GPL 的研讨会。该研讨会名为“自由软件许可和 GNU GPL”，将由 Patterson Belknap Webb & Tyler 的 FSF 外部顾问 Daniel Ravicher 和 FSF 执行董事 Bradley M. Kuhn 共同主持。
^"GNU GENERAL PUBLIC LICENSE". gplv3.fsf.org. Archived from the original on 2008-10-02. Retrieved 2012-06-25.^ “GNU 通用公共许可证”。 gplv3.fsf.org。原始存档于 2008-10-02。检索于 2012-06-25。
^Stallman, Richard. "Richard Stallman's Personal Site". Retrieved 2021-03-18. I continue to be the Chief GNUisance of the GNU Project. I do not intend to stop any time soon.^ 斯托曼，理查德。 “理查德斯托曼的个人网站”。检索于 2021-03-18。我将继续担任 GNU 项目的首席 GNUisance。我不打算很快停下来。
^Larabel, Michael (2011-10-15). "The Sad State Of FSF's High Priority Projects". Phoronix. Retrieved 2014-12-29. Long story short, being on the Free Software Foundation's high priority list really doesn't mean much with some of these "important" projects not even being actively developed or even discussed.^ 迈克尔·拉拉贝尔 (2011-10-15)。 “FSF 高优先级项目的悲惨状态”。凤凰。检索于 2014-12-29。长话短说，在自由软件基金会的高优先级列表中确实没有多大意义，因为其中一些“重要”项目甚至没有被积极开发甚至讨论。
^Larabel, Michael (2012-04-22). "Many FSF Priority Projects Still Not Progressing". Phoronix. Retrieved 2014-12-29. Most of the projects are basically not going anywhere. Many of them at the time were not really advancing in their goals, haven't had releases in a while, or coding hasn't even started. It's been more than a half-year and still there's no significant work towards clearing many of projects from the FSF list. ^ 迈克尔·拉拉贝尔 (2012-04-22)。 “许多 FSF 优先项目仍未取得进展”。凤凰。检索于 2014-12-29。大多数项目基本上没有进展。当时他们中的许多人并没有真正推进他们的目标，有一段时间没有发布，或者编码甚至还没有开始。已经半年多了，仍然没有从 FSF 列表中清除许多项目的重要工作。
^ Jump up to: abcThe first GNU's Bulletin ("GNU's Bulletin, Volume 1, No.1". Free Software Foundation. February 1986. Retrieved 2007-08-11.), indicates this list of people as round[ing] out FSF's board of directors.^ 跳转至： a b c The first GNU's Bulletin（“GNU's Bulletin, Volume 1, No.1”。自由软件基金会。1986 年 2 月。检索于 2007-08-11。），表明此人名单为 round[ing] out FSF 的董事会。
^The FSF annual filings with the Commonwealth of Massachusetts for 2002 ("2002 Annual Report for Free Software Foundation, Inc"(PDF). The Commonwealth of Massachusetts. 2002-12-17. Retrieved 2007-08-11.) show that De Icaza has left the board. Changes to board composition are usually made at the annual meeting; which occurred on February 25, 2002.^ 2002 年 FSF 向马萨诸塞联邦提交的年度报告（“2002 年自由软件基金会年度报告”（PDF）。马萨诸塞联邦。2002-12-17。2007-08-11 检索。）显示 De Icaza 已离开董事会。董事会组成的变动通常在年会上进行；发生在 2002 年 2 月 25 日。
^Moglen announced his intention to resign in his blog (Moglen, Eben (2007-04-23). "And Now ... Life After GPLv3". Retrieved 2007-08-11.). The resignation likely occurred at the 2007 annual meeting of the directors; the exact date of that meeting is unknown.^ Moglen 在他的博客中宣布了他的辞职意向（Moglen, Eben (2007-04-23)。“And Now ... Life After GPLv3”。2007-08-11 检索。）。辞职很可能发生在2007年度董事会议上；该会议的确切日期不详。
^"Kat Walsh joins FSF board of directors". fsf.org. Free Software Foundation, Inc. 21 March 2015. Retrieved 22 March 2015.^ “Kat Walsh 加入 FSF 董事会”。 fsf.org. Free Software Foundation, Inc.，2015 年 3 月 21 日。2015 年 3 月 22 日检索。
Article II, Sec. 1 - Number, Election and Qualification: The present members of the corporation shall constitute the voting members. Thereafter the voting members annually at its annual meeting shall fix the number of voting members and shall elect the number of voting members so fixed. At any special or regular meeting, the voting members then in office may increase the number of voting members and elect new voting members to complete the number so fixed; or they may decrease the number of voting members, but only to eliminate vacancies caused by the death, resignation, removal or disqualification of one or more voting members.
— Amended By-laws, Nov. 25, 2002, Free Software Foundation, Inc.
In addition to the right to elect Directors as provided in the bylaws and such other powers and rights as may be vested in them by law, these Articles of Organization or the bylaws, the Voting Members shall have such other powers and rights as the Directors may designate.
— Amended By-laws, Nov. 25, 2002, Free Software Foundation, Inc.
^The site member.fsf.org first appears in the Internet Archive in December 2002, and that site lists the date of the launch as 25 November 2002. "FSF Membership Page". The Internet Archive. Archived from the original on 2002-12-20.^ 网站 member.fsf.org 于 2002 年 12 月首次出现在 Internet Archive 中，该网站将发布日期列为 2002 年 11 月 25 日。“FSF 会员页面”。互联网档案馆。原始存档于 2002-12-20。
^Kuhn has an FSF-generated member link that identifies him as the first member on his web page. "Homepage of Bradley M. Kuhn". Bradley M. Kuhn. 2008-01-05. Retrieved 2008-01-05.^ Kuhn 有一个 FSF 生成的成员链接，在他的网页上将他标识为第一个成员。 “Bradley M. Kuhn 的主页”。布拉德利·库恩。 2008-01-05。检索于 2008-01-05。
^"The Party of Gno". Archived from the original on June 20, 2010. Retrieved 2010-06-22.: CS1 maint: unfit URL ()^ “侏儒党”。原始存档于 2010 年 6 月 20 日。2010-06-22 检索。
^trunk/copying on sourceforge.net/p/libdwg^ trunk/copying on sourceforge.net/p/libdwg
^Larabel, Michael (2013-01-24). "FSF Wastes Away Another "High Priority" Project". Phoronix. Archived from the original on 2016-11-09. Retrieved 2013-08-22. Both LibreCAD and FreeCAD both want to use LibreDWG and have patches available for supporting the DWG file format library, but can't integrate them. The programs have dependencies on the popular GPLv2 license while the Free Software Foundation will only let LibreDWG be licensed for GPLv3 use, not GPLv2.^ 迈克尔·拉拉贝尔 (2013-01-24)。 “FSF 浪费了另一个“高优先级”项目”。凤凰。原始存档于 2016-11-09。检索于 2013-08-22。 LibreCAD 和 FreeCAD 都想使用 LibreDWG，并且有补丁可用于支持 DWG 文件格式库，但无法集成。这些程序依赖于流行的 GPLv2 许可证，而自由软件基金会只会让 LibreDWG 获得 GPLv3 使用许可，而不是 GPLv2。
^ Jump up to: abProkoudine, Alexandre (26 January 2012). "What's up with DWG adoption in free software?". libregraphicsworld.org. Archived from the original on 9 November 2016. Retrieved 3 November 2013. [Assimp's Alexander Gessler:] "Personally, I'm extremely unhappy with their [LibreDWG's — LGW] GPL licensing. It prohibits its use in Assimp and for many other applications as well. I don't like dogmatic ideologies, and freeing software by force (as GPL/GNU does) is something I dislike in particular. It's fine for applications, because it doesn't hurt at this point, but, in my opinion, not for libraries that are designed to be used as freely as possible." [Blender's Toni Roosendaal:] "Blender is also still "GPLv2 or later". For the time being we stick to that, moving to GPL 3 has no evident benefits I know of. My advice for LibreDWG: if you make a library, choosing a widely compatible license (MIT, BSD, or LGPL) is a very positive choice."^ 跳转至：a b Prokoudine, Alexandre（2012 年 1 月 26 日）。 “在免费软件中采用 DWG 有什么问题？”。 libregraphicsworld.org。原始存档于 2016 年 11 月 9 日。检索于 2013 年 11 月 3 日。[Assimp 的 Alexander Gessler：]好吧。我不喜欢教条主义的意识形态，并且我特别不喜欢强制释放软件（如 GPL/GNU 所做的那样）。这对应用程序来说很好，因为在这一点上它没有伤害，但是，在我看来，不适用于旨在尽可能自由使用的图书馆。” [Blender 的 Toni Roosendaal：]“Blender 仍然是“GPLv2 或更高版本”。目前我们坚持这一点，据我所知，转向 GPL 3 没有明显的好处。我对 LibreDWG 的建议：如果你创建一个库，选择广泛兼容的许可证（MIT、BSD 或 LGPL）是一个非常积极的选择。”
^Prokoudine, Alexandre (2012-12-27). "LibreDWG drama: the end or the new beginning?". libregraphicsworld.org. Archived from the original on 2016-11-09. Retrieved 2013-08-23. [...]the unfortunate situation with support for DWG files in free CAD software via LibreDWG. We feel, by now it ought to be closed. We have the final answer from FSF. [...] "We are not going to change the license."^ Prokoudine，亚历山大 (2012-12-27)。 “LibreDWG 戏剧：结束还是新的开始？”。 libregraphicsworld.org。原始存档于 2016-11-09。检索于 2013-08-23。 [...] 通过 LibreDWG 在免费 CAD 软件中支持 DWG 文件的不幸情况。我们觉得，现在应该关闭了。我们得到了 FSF 的最终答复。 [...]“我们不会更改许可证。”
^Prokoudine, Alexandre (26 January 2012). "What's up with DWG adoption in free software?". libregraphicsworld.org. Archived from the original on 9 November 2016. Retrieved 3 November 2013. GPLv3 license. It doesn't work for end-user software, because they tend to use 3rd party components under different licenses that impose restrictions. FSF who are sole copyright holders of LibreDWG objected to relicensing. With regards to FreeCAD project and Yorik van Havre, its contributor, Richard Stallman stated:" You should not change the license of your library. Rather, it is best to make it clear to him what the conditions are." [...] Personally, I'm extremely unhappy with their [LibreDWG's — LGW] GPL licensing. It prohibits its use in Assimp and for many other applications as well. I don't like dogmatic ideologies, and freeing software by force (as GPL/GNU does) is something I dislike in particular. It's fine for applications, because it doesn't hurt at this point, but, in my opinion, not for libraries that are designed to be used as freely as possible.^ Prokoudine, Alexandre（2012 年 1 月 26 日）。 “在免费软件中采用 DWG 有什么问题？”。 libregraphicsworld.org。原始存档于 2016 年 11 月 9 日。2013 年 11 月 3 日检索。GPLv3 许可证。它不适用于最终用户软件，因为他们倾向于在施加限制的不同许可下使用 3rd 方组件。作为 LibreDWG 唯一版权持有者的 FSF 反对重新授权。关于 FreeCAD 项目及其贡献者 Yorik van Havre，Richard Stallman 表示：“你不应该更改你的库的许可证。相反，最好向他说明条件是什么。” [...] 就我个人而言，我对他们的 [LibreDWG's — LGW] GPL 许可非常不满意。它禁止在 Assimp 和许多其他应用程序中使用它。我不喜欢教条主义的意识形态，并且我特别不喜欢强制释放软件（如 GPL/GNU 所做的那样）。这对应用程序来说很好，因为此时它不会受到伤害，但在我看来，对于设计为尽可能自由使用的库来说则不然。
^"In Support of Richard Stallman". stallmansupport.org. Retrieved 8 February 2023.^ “支持理查德斯托曼”。 stallmansupport.org. 2023 年 2 月 8 日检索。
^Free Software Foundation (2005). "FSF honored with Prix Ars Electronica award". News Releases. Free Software Foundation. Retrieved 2006-12-10.^ 自由软件基金会 (2005)。 “FSF 荣获 Prix Ars Electronica 奖”。新闻发布。自由软件基金会。检索于 2006-12-10。
_auf_Debian_7_Wheezy_2015-04-02.png)
![[icon]](https://en.wikipedia.org/wiki/File:Wiki_letter_w_cropped.svg){kind=small}
